Classify documentation impact from a code diff and update affected documents.
npx skills add https://github.com/romiluz13/auto-pi --skill diff-driven-docs
Please help me install this Agent Skill. Skill: diff-driven-docs Source: https://github.com/romiluz13/auto-pi/tree/main/skills/diff-driven-docs Command: npx skills add https://github.com/romiluz13/auto-pi --skill diff-driven-docs
This Skill prevents documentation drift by evaluating how code changes affect business, technical, and audit documentation, ensuring updates are made only when genuinely needed.
Use the diff-driven-docs skill after completing a code change to classify its documentation impact and update only the necessary documents.
High-intent search queries and answers about installing and using this skill.
Updating documentation after a code change involves inspecting the diff to classify its impact across business, technical, and audit layers. You then edit only the targeted documents affected by the new behavior or APIs.
The best way to identify necessary technical docs updates is to evaluate the code diff impact level. This classification determines exactly which user-facing, technical, and audit documents require revisions before a pull request.
You need to update audit records after completing build phases but before commits or pull requests. This verifies whether documentation matches the implemented behavior for changes involving permissions or security updates.
Diff analysis verifies documentation accuracy by re-reading the updated documents against the implementation. This catches inaccurate claims by ensuring the text reflects the actual code changes and targeted edits made.
Yes, you can use diff analysis to target documentation updates specifically for architectural decisions. The impact classification ensures only documents genuinely needing updates for new behaviors or APIs are modified.
ConaryLabsAnalyze git changes to classify modifications and assess impact and risk.
stacklokAnalyze upstream releases and update documentation with source-verified change tracking.
TeiNamAutomate Laravel project verification for CI/CD pipelines.
githubnextClassify pull request diff impact on documentation using a three-layer deterministic and LLM model.
