Medox docs-up
Audit code changes on the current branch and update docs/ + .claude/rules/ to stay in sync. Run before /pr.
install
source · Clone the upstream repo
git clone https://github.com/spideystreet/medox
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/spideystreet/medox "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/docs-up" ~/.claude/skills/spideystreet-medox-docs-up && rm -rf "$T"
manifest:
.claude/skills/docs-up/SKILL.mdsource content
Skill: Sync Docs
Audit all code changes on the current branch vs main, then update documentation files to reflect those changes.
Steps
1. Identify what changed
git diff main...HEAD --name-only
Categorize changed files into impact zones:
| Changed path pattern | Docs impact |
|---|---|
| , |
| , |
| |
| , |
| , |
| , , |
| , |
| no docs change needed |
(other) | no docs change needed |
| (if new script) |
2. For each impacted doc, read it and check for staleness
For each doc file identified above:
- Read the current doc file
- Read the changed source files
- Compare: are there new entities (tools, models, assets, nodes) missing from the doc?
- Compare: are there renamed/removed entities still referenced in the doc?
- Compare: are there changed behaviors (e.g. new parameters, new strategies) not reflected?
3. Apply updates
For each stale doc:
- Add new entries to tables, diagrams, and source lists
- Update descriptions that no longer match the code
- Remove references to deleted entities
- Keep the existing style and structure of each doc file
Also check
.claude/rules/ files:
— tools table, node listagent.md
— asset graph, key files tablepipeline.md
— current Silver models listdbt.md
4. Report
After all edits, output a summary:
Docs synced: - docs/agent/tools.mdx — updated check_interactions section - docs/pipeline/overview.mdx — added new asset - (no changes needed for docs/dbt/overview.mdx)
If no docs need updating, report: "All docs are up to date."
Rules
- Never rewrite entire sections — make minimal, targeted edits
- Keep all docs in English (same as code comments)
- Do not touch
ordocs/introduction.mdx
unless the overall architecture changeddocs/quickstart.mdx - Do not commit — leave changes staged for the user to review before
/pr