speckit.diff

Generate structured markdown diff reports for specification artifacts.

63|13|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.diff
Source: https://github.com/compnew2006/Spec-Kit-Antigravity-Skills/tree/main/skills/speckit.diff
Command: npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compare two versions of a specification artifact and produce a structured diff report that highlights changes, aiding teams in quick review and traceability.

Core Features & Use Cases

  • Semantic diffing of sections and content to highlight added, removed, and modified information.
  • Report generation in a clear, structured markdown format suitable for review and documentation.
  • Flexible input supports direct file comparisons or HEAD-based comparisons when given a single path.

Quick Start

Provide two file paths to compare, and the tool will output a structured diff report.

Frequently Asked Questions about speckit.diff

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

FAQPage Schema
How do I generate a diff report comparing two versions of a specification artifact?

To generate a diff report for a specification artifact, provide two file paths for comparison and the tool outputs a structured markdown report highlighting added, removed, and modified content by section.

Can I compare a single spec file against HEAD without providing a second path?

Yes, you can compare a single spec file against HEAD. When no second file path is provided, the tool automatically performs a HEAD-based comparison to identify changes in the specification artifact.

What is semantic diffing for spec and plan documents?

Semantic diffing for spec documents analyzes changes by section rather than line-by-line, identifying precise added, removed, and modified information to produce structured reports with clear impact notes.

How do I review added and removed content in a specification version control workflow?

To review added and removed content in a specification version control workflow, run a semantic diff comparison to generate a structured markdown report that highlights specific modifications and provides impact notes.

Does the spec diff tool require any dependencies to compare plan artifacts?

No dependencies are required to compare plan artifacts. The tool operates independently to analyze specification files and generate structured diff reports for version control and review.

What is the best way to trace modifications between specification versions for team review?

The best way to trace specification modifications for team review is generating a structured diff report that breaks down changes by section with impact notes, ensuring quick review and traceability across versions.