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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.qwen/skills/docs-update-from-diff/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, actionable instruction-only skill with a clear sequenced workflow and an explicit verification step. Main improvement is de-duplicating the doc-path-consumer guidance between step 5 and the heuristics section.

Suggestions

Consolidate the qc-helper / .qwen/skills doc-path-consumer guidance into a single location (either step 5 or 'Practical heuristics') to remove the near-duplicate paragraph and tighten conciseness.

Consider moving the detailed qc-helper index-table instructions into references/docs-surface.md and keeping only a one-line pointer in the body, strengthening progressive disclosure.

Add an explicit verify-and-retry loop in step 5 (e.g., 'if a stale reference is found, fix it and re-scan') to lift workflow_clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without explaining git or docs concepts; the only trimming opportunity is the qc-helper/doc-path-consumer guidance repeated in both step 5 and 'Practical heuristics', which is a minor instance of over-explanation.	4 / 5
Actionability	Concrete, executable guidance throughout — specific commands ('git status --short', 'git diff --stat'), concrete paths ('docs/users/**', 'docs/users/configuration/settings.md', '_meta.ts'), and a real referenced file — with only minor gaps in coverage of edge cases.	4 / 5
Workflow Clarity	A clear five-step sequence culminates in an explicit 'Cross-check before finishing' validation step with concrete checks (search for old names, confirm _meta.ts entries, re-read against the diff); not a full validate-fix-retry feedback loop, so it stops short of the top anchor.	4 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled one-level-deep reference ('Read references/docs-surface.md before editing if...'); the body inlines a fairly detailed qc-helper paragraph that could arguably live in the reference, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it states a clear purpose, uses third-person voice, and pairs concrete actions with explicit trigger phrases. Minor gains are possible by broadening the named actions beyond 'review' and 'update'.

Dimension	Reasoning	Score
Specificity	Names the domain (syncing docs to code) and two concrete actions — 'Review local code changes with git diff' and 'update the official docs under docs/ to match' — but does not enumerate the fuller range of doc-update actions, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Explicitly answers both what ('Review local code changes with git diff and update the official docs under docs/ to match') and when (a 'Use when...' clause listing concrete triggers and quoted phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Quotes natural phrases users would say ('git diff', 'local changes', 'update docs', 'official docs') plus variations like 'sync docs with local changes' and 'document current uncommitted work', giving good but not exhaustive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	The git-diff-to-docs niche with distinctive triggers ('git diff', 'local changes') is mostly distinct, with only minor overlap risk against generic docs-maintenance skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: QwenLM/qwen-code
Path: .qwen/skills/docs-update-from-diff/SKILL.md
Commit: 054eabb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.