specs-compliance

Name: specs-compliance
Availability: InStock
Author: SpecD

Audit specs against code implementations to detect drift and verify test coverage.

12|Updated Feb 28, 2026

Search Tags:#testing #compliance #code-review #read-only #specs #dependency-check #GitNexus

Ready to run

npx skills add https://github.com/specd-sdd/SpecD --skill specs-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specs-compliance
Source: https://github.com/specd-sdd/SpecD/tree/main/dev/ai-agents/skills/specd-specs-compliance
Command: npx skills add https://github.com/specd-sdd/SpecD --skill specs-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits specs against code implementations in SpecD projects, highlighting discrepancies without modifying code.

Core Features & Use Cases

Read-only spec-vs-code compliance reviews
Multi-mode audit: full audit, single spec, changed files, or PR diff
Detailed per-spec reporting including test coverage and dependency checks

Quick Start

Run the auditor with no arguments to perform a full audit of all specs.

Frequently Asked Questions about specs-compliance

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

FAQPage Schema

How do I audit specs against code implementations for drift?▼

Spec compliance auditing detects drift between specifications and code implementations by mapping specs to code using GitNexus. It verifies test coverage and validates dependencies without modifying code.

Can I check spec compliance for only changed files or PR diffs?▼

Yes, spec compliance auditing supports multiple modes including single spec, changed files, and PR diff audits. You can run targeted checks to surface discrepancies and test coverage gaps for specific code changes.

What is the best way to verify test coverage and dependency checks in a read-only code review?▼

Read-only spec compliance audits verify test coverage and validate dependencies by mapping specifications to existing code. They generate detailed per-spec reports highlighting discrepancies without modifying the codebase.

Does the spec-vs-code auditor modify my code during dependency checks?▼

No, the spec compliance auditor operates in a strictly read-only manner. It surfaces discrepancies and validates dependencies using GitNexus code intelligence without modifying your codebase.

How do I perform a full audit of all specs in a SpecD project?▼

To perform a full audit of all specs in a SpecD project, run the auditor with no arguments. It will map all specs to code implementations, check dependencies, and generate detailed per-spec reports.

What is spec drift detection and when do I need it for code review?▼

Spec drift detection identifies when code implementations diverge from their original specifications. You need it during code review to verify test coverage, validate dependencies, and catch discrepancies before merging changes.