spec-audit

Detects inconsistencies across DESIGN/*.md files and generates structured reports.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nok0321/claude-pipeline --skill spec-audit-nok0321
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-audit
Source: https://github.com/nok0321/claude-pipeline/tree/main/skills/spec-audit
Command: npx skills add https://github.com/nok0321/claude-pipeline --skill spec-audit-nok0321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DESIGN/*.md 仕様書間の矛盾(型名揺れ、フィールド不一致、API契約不一致、依存循環、DBスキーマ不整合、用語不統一、定数不整合)を検出し、自己検証を支援します。

Core Features & Use Cases

  • DESIGN/*.md の整合性を横断的に検出するデザイン監査
  • 仕様書間の型名・フィールド名の揺れや API 仕様の不整合を特定
  • 更新後の PR 前チェックや design-phase での自動検証をサポート

Quick Start

Run spec-audit to validate DESIGN/*.md consistency and surface issues before PRs.

Frequently Asked Questions about spec-audit

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

FAQPage Schema
How do I check design specs for inconsistencies across markdown files?

A design audit checks DESIGN/*.md files for inconsistencies by detecting type name drift, field mismatches, and API contract discrepancies. It validates alignment during the design phase and surfaces drift before merges.

What is design drift and how do I catch it before a PR?

Design drift happens when updating DESIGN/*.md files introduces conflicting specifications. Catch it before a PR by running a consistency check that identifies type or field name agreement issues, cross-document reference errors, and dependency cycles.

Can I validate API contract consistency across multiple design documents?

You can validate API contract consistency across multiple design documents. The audit detects mismatches in API specifications, cross-document references, and dependency cycles, exporting a structured report of the findings.

Does the design audit detect dependency cycles in spec files?

The design audit detects dependency cycles in spec files. It checks cross-document references and dependency loops alongside type and field name agreement, ensuring your DESIGN/*.md files maintain structural and logical alignment.

What is the best way to automate design-phase validation for markdown specs?

Automate design-phase validation for markdown specs by running a consistency check after adding or updating DESIGN/*.md files. This surfaces type name drift, DB schema mismatches, and terminology inconsistencies before PR review.