How does Audit Trail store decision history?

Audit Trail uses a multi-layer storage approach: in-memory for active sessions, local JSON files in the .claude/coherence-audit/ folder for persistence, and formatted Git commit messages for permanent repo history.

Does it integrate with my existing Git workflow?

Absolutely. Audit Trail automatically formats Git commit messages to include session IDs, iteration counts, and critic verdicts, making your git log a self-documenting audit trail.

Can I search for specific security critic rejections?

Yes, you can use commands like '/audit-trail search security critic rejections' to find every instance where the security critic vetoed a change and see the underlying reasoning.

What is Exposure Analysis?

Exposure analysis is a feature that identifies all files or sessions that depend on a specific decision, allowing you to assess the risk and impact of changing core logic.

Audit Trail

Name: Audit Trail
Author: reggiechan74

byreggiechan74

•

Security & Testing

Provides full traceability for code decisions by documenting rationale, tracking changes, and enabling bidirectional history traversal.

The Audit Trail skill for Claude Code provides a robust framework for tracking and searching the decision history behind code changes verified through coherence checks. It enables developers to perform bidirectional traversal—understanding the 'why' behind past architectural decisions and identifying 'what' happened afterward through downstream impact analysis. By persisting detailed logs in local JSON files and embedding rationale directly into git commit messages, it ensures long-term project maintainability, compliance, and clear accountability for every AI-assisted code iteration.

Key Features

01Git integration that embeds decision rationale and critic approvals in commits

02Advanced search capabilities by critic verdict, file path, and date range

03Bidirectional traversal to trace decisions forward and backward in time

043 GitHub stars

05Exposure analysis to identify downstream impacts of corrected facts or logic

06Persistent file-based logging in .claude/coherence-audit/ directory

Use Cases

01Conducting security or compliance audits to verify why specific code patterns were approved or vetoed

02Onboarding new team members by providing a searchable history of architectural trade-offs

03Performing impact assessments when refactoring core modules to see which files depend on previous decisions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add reggiechan74/cc-plugins audit-trail

For use in Claude.ai and ChatGPT

Download Skill