diff-skill

Diff reachable Markdown files from SKILL.md between git refs and report degradations.

147|31|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/serpro69/claude-toolbox --skill diff-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-skill
Source: https://github.com/serpro69/claude-toolbox/tree/main/kodex-plugin/skills/diff-skill
Command: npx skills add https://github.com/serpro69/claude-toolbox --skill diff-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to detect degradations and complexity increases when a skill's Markdown instructions change, by diffing the HEAD version against the working tree and tracing reachable files from SKILL.md.

Core Features & Use Cases

  • Asymmetric degradation checks: only regressions count, additions and clarifications are neutral.
  • Reachable-file diffing: follows links from SKILL.md to build the comparison surface.
  • Automated reporting: writes a structured report under docs/reviews/diff-skill/ and provides an inline summary for quick review.
  • Supports multi-ref comparisons (default HEAD → WORKTREE) and easy invocation for other refs.

Quick Start

Run the diff-skill tool to compare a skill's SKILL.md between two git refs and generate an annotated report.

Frequently Asked Questions about diff-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect instruction degradations when updating skill Markdown files?

To detect instruction degradations in skill Markdown files, diff the HEAD version against the working tree to identify complexity regressions. The tool applies asymmetric judgment where only regressions count, while additions and clarifications remain neutral.

How does diffing SKILL.md trace reachable files for quality reviews?

Diffing SKILL.md traces reachable files by following links from the entry point to build the complete comparison surface. It outputs the full contents of all reachable files on both refs and identifies any missing links during the degradation check.

Can I compare skill instructions between different git refs besides HEAD and the working tree?

Yes, you can compare skill instructions between different git refs. While the default comparison is asymmetric from HEAD to WORKTREE, the tool supports multi-ref comparisons and allows easy invocation for other refs to generate annotated reports.

What is the best way to report complexity regressions in Markdown instructions?

The best way to report complexity regressions is to generate a structured report under docs/reviews/diff-skill. This report includes an inline summary for quick review and provides annotated details of all degradations found during the diff.

Does asymmetric judgment affect how additions to Markdown instructions are evaluated?

Asymmetric judgment ensures that additions and clarifications to Markdown instructions are treated as neutral during the diff. Only actual regressions and complexity increases count as degradations, preventing false positives when expanding skill documentation.

Why are missing links identified when diffing a skill's SKILL.md?

Missing links are identified when diffing SKILL.md because the tool traces all reachable files from the entry point to construct the comparison surface. This ensures broken references are reported alongside complexity regressions in the final review.