skill-doc-sync
FeaturedPost-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.
Install
Quality Score: 99/100
Skill Content
Details
- Author
- nyldn
- Repository
- nyldn/claude-octopus
- Created
- 7 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
doc-sync
Sync all project docs after a code change — scans every doc for stale references, updates affected sections. Triggers: "sync docs" | "doc sync" | "sync plugin docs" | "update skill docs".
update-docs
Audit and update every documentation surface in the APEX repo against the current state of skills, steering workflows, README marker tables, and the Docusaurus site under misc/website/. After any change to a skill (rename, retire, add, edit description), walk the repo, re-run script-managed surfaces if their --check fails, and reason through every tracked prose *.md to catch references that need updating. Use after adding/removing/renaming a skill, after editing SKILL.md frontmatter, after editing README marker blocks, or before publishing a docs change. Also use when the user says "update docs", "sync docs", "check docs", "run update-docs", or mentions that documentation might be stale.
sync-docs
Sync plans, docs, and instruction files after behavior, commands, contracts, or workflows change. Also covers harness-internal consistency after skill, hook, rule, or script changes. Invoked after /test and before /cross-review as the doc-maintainer agent; inline execution is only a dispatch-failure fallback.