skills.rest
surfingalien
surfingalienCOMMUNITY
Explore all skills by this author →
GitHub

check

Detects drift between SPEC.md and code by auditing invariants, interfaces, and task status.

1|Updated May 6, 2026
Search Tags:#specification#verification#code audit#read-only#interface validation#invariants#spec drift
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill check-surfingalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/ck%3Acheck
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill check-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases drift away from their written specifications over time, leaving stale docs and hidden inconsistencies. This Skill performs a read-only audit that diffs SPEC.md against the actual code and reports violations grouped by severity, without modifying anything. ## Core Features & Use Cases - Invariant Checking (§V): Translates each spec invariant into a verifiable claim, greps the code, and classifies it as HOLD, VIOLATE, or UNVERIFIABLE with file:line evidence. - Interface Auditing (§I): Compares implemented API and CLI surfaces against the spec, flagging MATCH, DRIFT, MISSING, or EXTRA items. - Task Status Verification (§T): Validates that tasks marked complete actually have supporting code, flagging stale entries. - Use Case: Before a release, ask whether the code still matches the spec; receive a severity-grouped drift report with exact file:line citations and remedy hints pointing to the spec or build skills. ## Quick Start Ask the assistant to check drift between SPEC.md and the current code and report any violations.

Frequently Asked Questions about check

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

FAQPage Schema
How do I check if my code still matches its specification?▼

Run a drift check that reads SPEC.md and audits each invariant, interface, and task against the code. The report classifies every item as holding or drifting, with file:line evidence for each violation.

What is spec drift in software development?▼

Spec drift occurs when implementation diverges from the written specification over time. It includes violated invariants, changed API shapes, missing features, and tasks marked complete without supporting code.

Can the drift check audit only specific spec sections?▼

Yes, invocation arguments scope the audit: §V checks invariants only, §I checks interfaces, §T audits task status versus code, and --all runs all three checks together.

Does the drift detector modify my code or spec file?▼

No, the check is strictly read-only. It reports violations and suggests one-line remedy hints, such as invoking a spec or build skill, but never edits SPEC.md or source code itself.

What happens when an invariant cannot be verified automatically?▼

The invariant is classified as UNVERIFIABLE rather than passed or failed. This typically occurs when no test or code path covers the claim, and the report notes the gap explicitly.

Related Skills

Explore More Software Engineering Skills→
Kushal9889Kushal9889

check

Checks code drift against SPEC.md and verifies invariants via scripts.

Community
Advanced
cliffthelincliffthelin

rulecheck

Scan repositories for CLAUDE.md rule violations and open a pull request.

Community
Advanced
L3DigitalNetL3DigitalNet

verification-before-completion

Require fresh test, linter, and build verification before reporting completion.

Community
Advanced
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced