Audit Trail
Record and query project decisions with timestamps, rationale, and consequences.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/doncheli-audit-trail-doncheli/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
Record and query the decision log for a project. Activate when user mentions "audit", "trail", "log decisions", "decision history", "why was this decided", "ADR", "architecture decision".
What this skill does
Don Cheli: Audit Trail
Instructions
- Maintain a structured decision log at
.dc/decisiones.md - When invoked to record a decision:
- Extract: decision title, date, context, options considered, chosen option, rationale, consequences
- Append as a new ADR-style entry (numbered, never edited after creation)
- Tag with: [technical | product | process | security]
- When invoked to query the log:
- Accept a keyword or topic and return matching entries
- Show: decision ID, date, title, one-line summary, and link to full entry
- When invoked to review a past decision:
- Find the entry, show full context, and ask if a superseding decision should be recorded
- Never overwrite the original — only append a "Superseded by ADR-XXX" note
- Surface related decisions automatically when the user is working on a feature that has prior ADRs
- Each entry is immutable once committed — audit integrity is the primary constraint
Output Format
## ADR-007 — 2026-03-28
**Title:** Use PostgreSQL over MongoDB for user data
**Tags:** [technical] [database]
**Status:** Accepted
### Context
Needed a persistence layer for structured user profiles with relational queries.
### Options Considered
- MongoDB: flexible schema, horizontal scale
- PostgreSQL: ACID, relational queries, mature ecosystem
### Decision
PostgreSQL — relational guarantees outweigh schema flexibility for this use case.
### Consequences
- Migrations required for schema changes
- Scales vertically before needing sharding
Related skills
Generative Code Art
anthropics
Create algorithmic art with p5.js using randomness and interactive parameters.
Poster & Visual Design
anthropics
Create original posters and visual art in PNG and PDF formats.
Claude API Helper
anthropics
Build, debug, and optimize Claude API applications with caching and model migration support.
Documentation Co-Authoring
anthropics
Guide structured workflows for writing docs, proposals, and technical specs collaboratively.