gza-spec-review-all

Audit specs in specs/ against the codebase and generate a findings report.

11|1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-spec-review-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gza-spec-review-all
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-spec-review-all
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-spec-review-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate that specifications align with the current codebase, reducing drift between docs and implementation.

Core Features & Use Cases

  • Automated spec auditing against codebase to identify outdated or aspirational content.
  • Generates a prioritized report highlighting discrepancies with pointers to exact locations in specs/ and code.
  • Supports triaging specs during release cycles and after major refactors.

Quick Start

Run the spec-review-all skill against your repository to audit specs in specs/ and produce a findings report.

Frequently Asked Questions about gza-spec-review-all

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

FAQPage Schema
How do I check if my specs match the current codebase implementation?

To check if specs match the codebase, audit the specs/ directory against the actual implementation to surface outdated or aspirational content. This process generates a structured report with actionable findings highlighting discrepancies and exact locations.

What is the best way to automate spec review for outdated documentation during a release cycle?

Automating spec review during release cycles involves reading specifications and the codebase to generate a prioritized report of discrepancies. This identifies which specs reflect current implementation versus old references or aspirational features.

How do I verify spec accuracy after a major codebase refactor?

Verify spec accuracy after refactoring by running an automated audit to compare specs/ against the updated codebase. This determines which specifications still reflect the current implementation and highlights outdated references with exact pointers.

Can I identify aspirational content in my specs that isn't actually implemented?

You can identify aspirational content by auditing specifications against the actual codebase. The audit generates a structured findings report that distinguishes implemented features from outdated or unfulfilled aspirational references.

Does spec auditing work without specific version control dependencies?

Yes, spec auditing works without specific version control dependencies. The process reads the specs/ directory and the current codebase directly to produce a prioritized report of alignment discrepancies for code reviews.

Why does my specifications documentation drift from the actual codebase implementation?

Documentation drifts from the codebase when specs are not continuously validated after updates. Running an automated spec audit identifies these discrepancies by comparing the specs/ directory against the actual implementation to surface outdated content.