Audit user-facing documentation for drift from code changes.
npx skills add https://github.com/juxt/claude-plugins --skill weed-docs
Please help me install this Agent Skill. Skill: weed-docs Source: https://github.com/juxt/claude-plugins/tree/main/plugins/chalk/skills/weed-docs Command: npx skills add https://github.com/juxt/claude-plugins --skill weed-docs
When code changes such as renamed APIs, updated CLI flags, or removed features are made, user-facing technical documentation often falls out of sync, leading to outdated information for end users and wasted time manually cross-referencing code diffs against docs content.
Use the weed-docs skill to audit your project's user-facing documentation for drift against your current unmerged code changes and receive a prioritized list of pages that need updates.
High-intent search queries and answers about installing and using this skill.
To audit technical docs for code drift, scope the audit to your current branch diff or custom commit ranges to identify documentation needing updates due to API renames, signature changes, or removed features. You receive a page-grouped punch list of flagged items.
Finding missing documentation for new public APIs involves detecting new public surfaces in your code changes and cross-referencing them against existing docs. This process outputs a confidence-classified punch list highlighting coverage gaps for undocumented features.
Yes, documentation drift detection cross-references GitHub issues, PR discussions, and issue tracker context to add rationale to flagged items. This enriches bare coverage gaps with actionable, context-aware tasks detailing why the documentation update is necessary.
You can scope a documentation audit by defaulting to the current branch's diff against its base, or by providing custom commit ranges, specific commits, and targeted file paths. This narrows the audit scope to surface only relevant documentation candidates for review.
The best way to track API change impact on user-facing docs is to run an intelligent surface detection audit that identifies modified public APIs and updated error messages. It produces a prioritized punch list classifying items by high, medium, or coverage gap confidence levels.
No, this documentation audit does not modify any documentation files. It strictly analyzes your code modifications and cross-references issue context to produce a read-only, confidence-classified punch list of pages that require manual review and updates.
zapierGenerate Conventional Commits with Jira context and push changes.
mishrasanjeevAnalyze code diffs to validate documentation alignment with deployed code.
diiviikk5Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.
agent-shIdentify and summarize plan, documentation, issue, and scope drift in software projects.
