docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
Best for feature development teamsWorks with GitHubLow risk
⌘source
- author
@QwenLM- repo
- QwenLM/qwen-code
- language
- TypeScript
★24kstars
2.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Updates docs from local git diffs
- ·Treats current code as source of truth
- ·Scopes changes to docs/ directory only
- ·Derives documentation impact from code changes
- ·Focuses on non-doc changes first
- ·Uses existing docs pages when possible
Use Cases
- →Documenting current uncommitted work before a commit
- →Syncing documentation after implementing a new feature
- →Updating docs following a code refactor
- →Keeping official documentation aligned with local code changes
- →Ensuring docs reflect renamed or removed behaviors
Best for
- ✓feature development teams
- ✓maintainers updating docs
- ✓code review workflows
Not ideal for
- !one-off documentation tasks
- !projects without git
- !non-technical documentation
FAQs
name
docs-update-from-diff
description
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
Docs Update From Diff
Overview
Inspect local diffs, derive the documentation impact, and update only the repository's docs/ pages. Treat the current code as the source of truth and keep changes scoped, specific, and navigable.
Read references/docs-surface.md before editing if the affected feature does not map cleanly to an existing docs section.
Workflow
1. Build the change set
Start from local Git state, not from assumptions.
- Inspect
git status --short,git diff --stat, and targetedgit diffoutput. - Focus on non-doc changes first so the documentation delta is grounded in code.
- Ignore
README.mdand other non-docs/content unless they help confirm intent.
2. Derive the docs impact
For every changed behavior, extract the user-facing or developer-facing facts that documentation must reflect.
- New command, flag, config key, default, workflow, or limitation
- Renamed behavior or removed behavior
- Changed examples, paths, or setup steps
- New feature that belongs in an existing page but is not mentioned yet
$install
1-click copynpx skills add QwenLM/qwen-code --skill docs-update-from-diffSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.