Detect documentation drift across README, SPEC, and PRODUCT files.
npx skills add https://github.com/rishith-c/staple --skill doc-maintenance-rishith-c
Please help me install this Agent Skill. Skill: doc-maintenance Source: https://github.com/rishith-c/staple/tree/main/.agents/skills/doc-maintenance Command: npx skills add https://github.com/rishith-c/staple --skill doc-maintenance-rishith-c
Audit and align top-level documentation with evolving features to prevent drift between README, SPEC, and PRODUCT documents.
Run the maintenance pass to audit docs and generate a PR with drift fixes.
High-intent search queries and answers about installing and using this skill.
Documentation drift between README.md, doc/SPEC.md, and doc/PRODUCT.md is identified by auditing core docs against evolving features and surfacing classified inaccuracies for review.
The best way to fix outdated documentation is to propose minimal, non-destructive edits that maintain voice and consistency, then generate a dedicated branch and pull request with the patches.
You generate a pull request for documentation updates by running a maintenance pass that classifies drift, proposes patches, creates a branch, and opens a PR with a concise changelog of fixes.
Yes, you can audit docs for drift without destructive changes because the tool proposes minimal, non-destructive edits routed through a dedicated branch and pull request rather than direct commits.
You need to run a documentation maintenance pass when evolving features cause drift across your README, SPEC, and PRODUCT documents, requiring alignment to prevent inaccuracies.
kangnam7654Audit documentation drift against git history and open a PR.
srirajkAnalyze git history to produce a structured PR risk profile.
AnveioAutomate GitHub pull request creation, reviews, feedback, and merges via gh CLI.
adolfoaranaes12Validate architecture documents against a comprehensive checklist and generate quality scores.
