Every design choice leaves a trail. This skill helps you follow that trail from the first idea to the final code. It searches through conversations, handoffs, git history, and stored artifacts to piece together how a decision was made.
You get a clear timeline of events. Each event shows what changed, why it changed, and who made the change. All claims are backed by direct links to the evidence. This makes it easy to understand the reasoning behind any feature or architecture.
The trace skill works best with concepts like a feature name or a keyword. It produces a report with dates and sources. Teams use it to learn from past decisions and avoid repeating mistakes.
Global
mkdir -p ~/.claude/skills/traceProject
mkdir -p .claude/skills/traceSource Repository
Lark Baselarksuite/cli
Simplify your Lark Base data with tables, fields, records, and views
Lark Wikilarksuite/cli
Manage your Lark Wiki spaces, members, and documents with simple commands
Grillingmattpocock/skills
Test your plan thoroughly with clear step-by-step interview questions
Analyze Projectlllllllama/rigorpilot-skills
Safe read-only analysis of deep learning repos for understanding and risk detection
Ai Research Reproductionlllllllama/rigorpilot-skills
Faithful reproduction of deep learning research with auditable steps and minimal changes
Repo Intake And Planlllllllama/rigorpilot-skills
Scan a repo, find commands, and get a simple reproduction plan
Minimal Run And Auditlllllllama/rigorpilot-skills
Capture evidence from deep learning runs and create standardized audit reports
Obsidian Vaultmattpocock/skills
Search create and organize notes with wikilinks and index notes easily