888wing/codetape
The flight recorder for AI coding — keeps your docs in sync with your code
Platform-specific configuration:
{
"mcpServers": {
"codetape": {
"command": "npx",
"args": [
"-y",
"codetape"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
The flight recorder for AI coding — keeps your docs in sync with your code.
[](https://www.npmjs.com/package/codetape) [](https://github.com/888wing/codetape/blob/main/LICENSE) [](https://nodejs.org)
A Claude Code skill that automatically maintains documentation as AI agents modify your codebase. Zero dependencies. Fully local.
A single Claude Code session can modify 40+ files across your project. When the session ends, your README, CHANGELOG, and architecture docs remain frozen in the past. Future-you opens the project a week later and has no idea what happened. Future AI sessions hallucinate against stale docs. The gap between code reality and written documentation grows with every session.
Codetape captures the semantic meaning of code changes — not just diffs, but *why* things changed — and keeps your documentation synchronized. It turns Claude into a code historian that records traces, detects drift, and regenerates docs on command. Everything stays local. No cloud, no accounts, no runtime dependencies.
npx codetape init # Set up tracking in your project# ... make some code changes with Claude Code ...
/trace # Record what changed and why
/trace-sync # Update your docs automaticallyThat's it. Your README, CHANGELOG, and ARCHITECTURE.md stay in sync.
| Command | Description | |---------|-------------| | /trace | Record a semantic trace of recent changes | | /trace-sync | Sync documentation from traces | | /trace-review | Detect documentation drift | | /trace-map | Generate architecture docs with dependency graphs | | /trace-log [component] | Query change history | | /trace-commit | Generate conven
Loading reviews...