Skip to main content
skill CX Codex

diff-skill — Claude Code skill: what it does, how to install

Diffs two revisions of a skill's markdown instructions and flags the edits that weaken a rule or add avoidable complexity. Useful before you accept changes to a skill you rely on.

no license ★ 155 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add serpro69/claude-toolbox --skill diff-skill -a claude-code
Open on GitHub

What diff-skill does

Point it at a skill and it compares the markdown that drives that skill across two revisions. The check runs one way: a dropped requirement, a softened rule, a missing verification step or a broken link counts as a regression, while fresh clarifications and extra examples do not. Content that moved but survived the edit stays neutral. Complexity is split too: what the edit introduced affects the verdict, and older issues are listed separately as suggestions.

By default it diffs HEAD against the working tree, and you can name other refs in the prompt. Starting from SKILL.md it follows the markdown links and covers every file it can reach, so a rule buried in a reference file still gets compared. Output lands in docs/reviews/diff-skill/<slug>-<sha-a>-<sha-b>.md, plus a short inline summary with the verdict, the finding counts and the path.

The shortcut $kk:diff-skill <skill-name> resolves klaude-plugin/skills/<skill-name>/SKILL.md, and asks you for the directory when that file is missing. Phases are strictly ordered: the skill reads its own diff-process.md first and won't touch the target before that. Findings get indexed in the capy knowledge base under kk:review-findings, but only when there is something to report.

What it helps with

  • catch a requirement that vanished during an instruction rewrite
  • tell a weakened constraint apart from a harmless clarification
  • review every linked file a skill pulls in, not just SKILL.md
  • keep older complexity issues from sinking the verdict on a new edit
  • get a written report with the path and the number of findings

Example prompts for the agent

  • Diff the deploy-guard skill against its last commit and list anything that got weaker
  • Run $kk:diff-skill commit-style and tell me whether the edit introduced a regression
  • Compare HEAD~2 with the working tree for the release-check skill

How to install diff-skill

1Skills CLI (Vercel)

npx skills add serpro69/claude-toolbox --skill diff-skill -a claude-code

2Manually: put the files in place

~/.claude/skills/diff-skill/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/diff-skill/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about diff-skill

How do I install diff-skill in Claude Code?

Run npx skills add serpro69/claude-toolbox --skill diff-skill -a claude-code. The skill file ends up at ~/.claude/skills/diff-skill/SKILL.md.

What does diff-skill do?

It compares two revisions of a skill's markdown instructions and reports whether degradations or extra complexity came in. Along the way it writes a report under docs/reviews/diff-skill/ and prints a short summary.

Which revisions does it compare by default?

HEAD against the working tree. You can name other refs in the prompt.

Similar skills

All skills for Code review and refactoring →

From the same set30

The whole set →
review-tool The review-tool skill checks tool configuration files against project schemas and reports violations. Use it when you need a full scan that continues after errors appear. CX Codex +1 ★ 155repo stars merge-docs merge-docs combines two doc sets for one feature into one: design, plan and tasks. Handy when design ran twice and you need a single version to build from. CX Codex +1 ★ 155repo stars isolated isolated — a command that runs code review through a separate spec-reviewer sub-agent with no authorship bias. Surfaces gaps between documentation and implementation by comparing them from scratch. CX Codex +1 ★ 155repo stars isolated The command checks an answer by assigning separate verification questions to isolated sub-agents. Use it to review factual claims or investigate code in a project. CX Codex +1 ★ 155repo stars isolated Runs an isolated multi-model code review on git changes. Evaluates security, compatibility, and design rules across separate reviewers. CX Codex +1 ★ 155repo stars dependency-handling The dependency-handling skill makes an agent verify dependency details before writing code that uses them. It helps when adding or upgrading a library, API, IaC version, CRD, or container image. CX Codex +1 ★ 155repo stars migrate migrate — a slash command that takes a project off Task Master MCP and onto task files in markdown, carrying open tasks over before clearing the old setup. CX Codex +1 ★ 155repo stars document Updates project documentation and architectural decisions after delivering a feature or bug fix following profile guidelines. CX Codex +1 ★ 155repo stars

Project sponsors

Companies that keep this analytics open