Tracedocs
- 29 installs
- 3.2k repo stars
- Updated August 2, 2026
- davepoon/buildwithclaude
Turns any codebase into evidence-grounded Markdown docs plus a machine-readable index.json where every operational claim cites a source and confidence label.
About
Analyzes a codebase, builds an evidence map, and writes documentation manuals plus an index.json manifest, labeling each claim Verified, Inferred, Unknown, or Needs confirmation and never inventing deployment steps. A developer uses it to produce durable, traceable docs when onboarding to or handing off an unfamiliar codebase.
- Every operational claim cites a source file and confidence label
- Machine-readable index.json for AI-agent handoff
Tracedocs by the numbers
- 29 all-time installs (skills.sh)
- Ranked #938 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davepoon/buildwithclaude --skill tracedocsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 29 |
|---|---|
| repo stars | ★ 3.2k |
| Last updated | August 2, 2026 |
| Repository | davepoon/buildwithclaude ↗ |
What it does
Turns any codebase into evidence-grounded Markdown docs plus a machine-readable index.json where every operational claim cites a source and confidence label.
Files
tracedocs
Turn any codebase into an evidence-grounded documentation package (overview, operation, deployment, learning, architecture, API/data, troubleshooting, maintenance) plus a machine-readable index.json for AI agents. Every operational/deployment claim cites a source file and a confidence label (Verified / Inferred / Unknown / Needs confirmation); it never invents deployment steps and records gaps instead.
Full skill, references, templates, and a validated sample output: https://github.com/wxggzz/tracedocs (MIT).
When to Use This Skill
- Onboarding to, or documenting, an unfamiliar codebase
- Producing durable, in-repo docs for operation, deployment, and maintenance
- Preparing an AI-agent-ready knowledge handoff (with
index.json) - Turning a repo into a study guide whose claims are traceable to source
What This Skill Does
1. Analyzes the codebase (stack, scripts, entry points, env-var names, deploy signals, tests). 2. Builds an evidence map (source map, assumptions, generation log) with confidence labels. 3. Writes the Markdown manuals and an index.json manifest; never invents deployment steps. 4. Runs a quality check (paths exist, commands sourced, no secret values, gaps documented).
How to Use
Basic Usage
Use tracedocs to generate evidence-grounded study docs for this repository. Write the output to study-docs/.Example
User: "Document ./my-app with tracedocs"
The skill scans the repo and writes a study-docs/ package (00-10 manuals + index.json + _evidence/), citing each operational claim's source and labelling its confidence - and explicitly noting anything it cannot verify (for example, "no deployment configuration found in the repo").
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.451k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.391k15.9kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.387k15.9k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k72Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k72
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.267k192k