doc-maintenance Skill
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on Published by microsoft in amplifier-app-paperclip.
What is doc-maintenance Skill?
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Database workflows
- Security review
- Documentation
- Database workflows use cases
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use doc-maintenance Skill
- Use it for database workflows.
- Use it for security review.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: .agents/skills/doc-maintenance/SKILL.md
What it does
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on
Skill instructions
Doc Maintenance Skill Detect documentation drift and fix it via PR — no rewrites, no churn. When to Use - Periodic doc review (e.g. weekly or after releases) - After major feature merges - When asked "are our docs up to date?" - When asked to audit README / SPEC / PRODUCT accuracy Target Documents | Document | Path | What matters | |----------|------|-------------| | README | README.md | Features table, roadmap, quickstart, "what is" accuracy, "works with" table | | SPEC | doc/SPEC.md | No false "not supported" claims, major model/schema accuracy | | PRODUCT | doc/PRODUCT.md | Core concepts, feature list, principles accuracy | Out of scope: DEVELOPING.md, DATABASE.md, CLI.md, doc/plans/, skill files, release notes. These are dev-facing or ephemeral — lower risk of user-facing confusion. Workflow Step 1 — Detect what changed Find the last review cursor: bash Read the last-reviewed commit SHA CURSORFILE=".doc-review-cursor" if [ -f "$CURSORFILE" ]; then LASTSHA=$(cat "$CURSORFILE" | head
Explore related resources
Frequently asked questions
What is doc-maintenance?
doc-maintenance is a open-source AI agent skill with Copy skill directory. Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed.
Who is doc-maintenance best for?
doc-maintenance is best for reusing agent instructions, scripts, and references, database workflows, security review workflows, documentation workflows.
How do I install doc-maintenance?
Install or run doc-maintenance using Copy skill directory. Check doc-maintenance for the latest setup command.
Is doc-maintenance actively maintained?
doc-maintenance may need a closer maintenance check before production use.
Auto-fetched from GitHub.
