update-docs
/update-docs
Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
- Author
- transparent-pegasus ↗
- Repository
- herdrpowers ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
Original author description
Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
How it works
- Overview
- Scope
- Workflow
SKILL.md preview
--- name: update-docs description: "Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents." --- # Update Docs ## Overview Keep root-level Markdown docs under `docs/` aligned with the current codebase and config. Use `ROOT_DOCS.md` in this directory as the contract for what each root doc should contain. ## Scope - Edit only files matching `docs/*.md` - Do not edit files inside `docs/*/` - Leave generated or output directories alone, including planning directories, generated content directories, and other paths explicitly marked as outputs by the initialized repository. ## Workflow 1. Identify which root docs are affected by the change. 2. Check `ROOT_DOCS.md` to confirm each affected doc's role and boundaries. 3. Check the current source of truth in code, config, prompts, schemas, or git history. 4. Update only the sections that changed. 5. Keep terminology, tone, and structure consistent with the existing file. 6. Keep diffs minimal. Prefer surgical edits over rewrites. 7. If a doc conflicts with the source of truth, fix the doc.
Files in this package (2)
- ROOT_DOCS.md 3 KB
- SKILL.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · transparent-pegasus/herdrpowers | 90 | MIT |
| iuliandita/skills | 100 | MIT |
| benweese/playwright-ai-qa-agents | 100 | MIT |
| thefrederiksen/devthrottle | 100 | MIT |
| vercel/next.js | 100 | MIT |
| RubenGlez/rubstack | 100 | MIT |
| peteonrails/voxtype | 100 | MIT |
| tesseron-dev/tesseron | 100 | Apache-2.0 |
| tmj-90/gaffer | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version d84e51ee1d8e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100update-architecture
Update architecture markdown files. Use when user says "update architecture", "update arch docs", "sync architecture", or mentions updating architecture documentation. - 100docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes",… - 100documentation
Use this skill when the user asks you to write, update, or fix project documentation — READMEs, API docs, user guides, ADRs, or other Markdown docs. Also use when code changes need user-facing docs updates. Only write Markdown files; do not use for implementation, planning or test work. - 95update-docs-on-code-change
Automatically update README.md and documentation files when application code changes require documentation updates Triggers on: **/*.{md,js,mjs,cjs,ts,tsx,jsx,py,java,cs,go,rb,php,rs,cpp,c,h,hpp} - 100generate-theories
This skill should be used when the user asks to "generate theories", "theorize about", "what theories explain", "form scientific theories", "literature-driven theories", "hypothesize", "form hypotheses", "generate hypotheses", "what hypotheses explain", "run the theorizer", or… - 95docs-update
Assess documentation impact and update affected docs for a code, API, config, or operator workflow change. Use when a change affects documented behavior, when asked to update stale docs or reconcile docs with code, or when a decision or status recorded in plans or ADRs changed.…