docs-update
/docs-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. Do not use for trivial changes with no documented surface, or for drafting new product copy from scratch.
- Author
- agustinusnathaniel ↗
- Repository
- maestria ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- 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
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. Do not use for trivial changes with no documented surface, or for drafting new product copy from scratch.
Original author description
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. Do not use for trivial changes with no documented surface, or for drafting new product copy from scratch.
How it works
- 1. Scope the change and find sources
- 2. Assess each category separately
- 3. Edit only affected sources
- 4. Verify claims with repo tools
- 5. Summarize
SKILL.md preview
--- description: 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. Do not use for trivial changes with no documented surface, or for drafting new product copy from scratch. name: docs-update --- # Update Documentation You are the agent keeping docs truthful after a change. Work in order: scope the change, find the authoritative sources, assess each documentation category separately, edit only affected sources, verify every claim, then summarize. ## 1. Scope the change and find sources Name the behavior change (code, API, config, or operator workflow) and locate the authoritative sources that describe it: the changed code or config, its tests, and the docs that claim to cover it. Consult the environment for available tools and current help (repo scripts, `--help` output) instead of relying on remembered paths. ## 2. Assess each category separately Assess internal docs, user-facing docs, changelog or release notes, and changesets (where the repository uses them) separately. For each category, either update it or record a concise reason it needs no update. Keep the assessment proportionate to the change. Respect project documentation conventions, explicit docs opt-outs, and safety rules. The absence of docs is not permission to create a large new hierarchy. Do not invent ADRs for a trivial change or new requirements; update plans and ADRs only when a recorded decision or status actually changed, preserving the historical record with amendments rather than rewriting history. ## 3. Edit only affected sources Edit only the affected authoritative sources. Trim before adding: state each concept once, as the principle and how to check it rather than its origin story. Durable docs never live only in scratch or temporary locations. Generated docs are never patched by hand: edit the canonical input and regenerate through the authorized workflow when regeneration is available; when it is not, report the blocker instead of patching the output. ## 4. Verify claims with repo tools Verify factual claims against current code and config. Check that links resolve, examples run, and operator scripts or checks produce their expected success or failure signals, using the repository's existing tools. A local docs task completes without publishing: no mandatory PR, and no tool installs without user or project authorization. ## 5. Summarize Report the actual edits per category, the checks run with their results, and the unresolved gaps. Keep reference files alongside the main file only when a genuinely distinct branch needs them and the pointer stays reliable; one concise file is enough otherwise.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · agustinusnathaniel/maestria | 95 | MIT |
| mgiovani/cc-arsenal | 100 | MIT |
| gosuda/dalcom-skills | 100 | Apache-2.0 |
| OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
| aka-kika/akakika-skills | 100 | MIT |
| zcaceres/skills | 100 | MIT |
| agustinusnathaniel/maestria | 95 | MIT |
Database snapshot: 13.11.2026 · package version e7a8ca5bf4e1 (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-docs
Update public documentation in docs/public/ when features or tools change. Triggers on "/update-docs", "update docs", "update documentation". - 100docs-sync
Use when the user asks to update documentation after code or configuration changes, audit documentation drift, or prepare README, API, runbook, or release docs. Changes only affected documentation and verifies examples, links, contracts, and operational steps against source code. - 100update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change",… - 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. - 90update-docs
Check and update repository documentation before creating PRs/MRs. Scans for outdated docs, mermaid diagrams, README, API docs. Only runs for repos with docs.enabled=true in config.json. Use when user says "update docs", "check documentation". - 100safe-code-change
After a code change, find affected tests, update them to match new behavior, then run the full validation pipeline once. Use when the user has made or asked for a code change and wants to make sure nothing is broken.