一键导入
doc-maintenance
Use when code changes may affect documentation, when adding new features that need docs, or when reviewing documentation freshness
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when code changes may affect documentation, when adding new features that need docs, or when reviewing documentation freshness
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute safe Git workflows — branching, committing, resolving conflicts, and managing PRs
Use when controlling AI spend, token budgets, model routing, or workflow efficiency before scaling usage
Use when handling incidents, outages, severe regressions, or operational emergencies before attempting broad fixes
Use when investigating latency, throughput, resource saturation, or performance regressions before changing implementation details
Use when reviewing code, preparing a PR for review, or processing review feedback
Use when diagnosing bugs, test failures, or unexpected behavior before attempting any fix
| name | doc-maintenance |
| description | Use when code changes may affect documentation, when adding new features that need docs, or when reviewing documentation freshness |
Announce at start: "Following the doc-maintenance skill to keep docs in sync."
Every code change has a documentation blast radius. Map it before committing.
After any code change, check:
| Change Type | Docs to Update |
|---|---|
| New API endpoint | API docs, README (if public), CHANGELOG |
| Changed behavior | Inline comments, user-facing docs, CHANGELOG |
| New configuration | README, environment docs, config reference |
| Removed feature | All references, migration guide, CHANGELOG |
| Renamed entity | All references (grep for old name) |
If a feature doesn't have documentation yet:
| Signal | Action |
|---|---|
| PR has code changes but no doc updates | Check the blast radius map |
| "I'll update docs later" | Update now — later never comes |
| Docs describe behavior that no longer exists | Delete or update immediately |
| New feature merged without any documentation | Create minimum viable doc before next task |
| When | Invoke |
|---|---|
| Writing the code that needs docs | planning |
| Ready to submit docs with code | pr-writing |
| Reviewing existing doc quality | code-review |
For principles, rationale, anti-patterns, and examples:
guides/doc-maintenance/doc-maintenance.mdguides/documentation-guidelines/documentation-guidelines.md