speckit.diff

Compare two specification versions and generate a structured markdown diff report.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-diff-aniruddh2003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.diff
Source: https://github.com/aniruddh2003/ai-code-reviewer/tree/main/.agent/skills/speckit.diff
Command: npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-diff-aniruddh2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline the process of comparing and visualizing changes between different versions of a specification or plan document, enhancing the efficiency of review processes.

Core Features & Use Cases

  • Version Comparison: Compare any two versions of a spec or plan to identify additions, removals, and modifications.
  • Change Summary: Generate a clear, structured report outlining each change by section with impact analysis.
  • Quick Report Generation: Automated generation of a markdown diff report with no external tooling required.
  • Use Case: Perfect for project managers or developers comparing changes in a spec before a new feature release.

Quick Start

Run the speckit.diff skill to compare the current version of 'spec.md' with its previous version from commit 'abc123'.

Frequently Asked Questions about speckit.diff

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

FAQPage Schema
How do I compare two versions of a specification document?

Comparing two specification versions is done by running the skill against your current spec and a previous file or commit. It uses diff libraries to highlight added, removed, and modified content, outputting a structured markdown report.

Can I generate a markdown diff report for a spec without external tooling?

Generating a markdown diff report requires no external tooling here. The skill automates the comparison process internally and outputs a structured markdown file outlining each change by section.

What is the best way to track changes in project plans before a feature release?

Tracking changes in project plans is best handled by an automated specification comparison tool. It identifies additions, removals, and modifications between versions, providing a clear change summary with impact analysis for release preparation.

Does this diffing tool work with previous versions pulled from a specific commit?

This diffing tool works with versions pulled from a specific commit. You can run the skill to compare your current spec.md file against a previous version referenced by its commit hash.

How does specification comparison handle impact analysis for modified content?

Specification comparison handles impact analysis by categorizing added, removed, and modified sections. It generates a structured report outlining each change by section to help you understand the exact impact on the documentation.

Are there limitations when using version control diffs for documentation maintenance?

A limitation is that the tool strictly generates markdown reports, meaning you need a markdown viewer to read the results. It focuses on structural specification comparison rather than resolving complex git merge conflicts.