skills.rest
seeker71
seeker71COMMUNITY
Explore all skills by this author →
GitHub

spec-guard

Validate code changes against a spec's allowed file list.

3|Updated Feb 12, 2026
Search Tags:#code review#validation#compliance#scope creep#spec
One-click install
npx skills add https://github.com/seeker71/Coherence-Network --skill spec-guard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-guard
Source: https://github.com/seeker71/Coherence-Network/tree/main/.cursor/skills/spec-guard
Command: npx skills add https://github.com/seeker71/Coherence-Network --skill spec-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents scope creep by ensuring that code changes strictly adhere to the defined specifications, flagging any modifications made to files not explicitly listed in the spec.

Core Features & Use Cases

  • Scope Validation: Verifies that all file modifications and creations align with the "Files to Create/Modify" section of a spec.
  • Violation Reporting: Clearly identifies and lists any files changed that fall outside the approved scope.
  • Use Case: Before merging a pull request, use this Skill to confirm that the developer only modified the files they were supposed to, preventing accidental or intentional deviations from the project's requirements.

Quick Start

Validate that the current code changes are within the scope defined in the spec file.

Frequently Asked Questions about spec-guard

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

FAQPage Schema
How do I prevent scope creep during code review?▼

To prevent scope creep during code review, validate code implementation against a defined specification by flagging files modified outside the spec's allowed list.

What is spec compliance validation for pre-merge verification?▼

Spec compliance validation for pre-merge verification ensures code changes adhere to the defined specifications by checking modifications against an approved files list.

How do I check if modified files are outside the approved spec scope?▼

You can check if modified files are outside the approved spec scope by using validation logic that compares file changes against a spec template defining Files to Create/Modify.

Can I use spec validation for pull request merge checks?▼

Yes, you can use spec validation for pull request merge checks to confirm developers only modified explicitly listed files, preventing accidental or intentional deviations from requirements.

What do I need to define before validating code adherence to spec?▼

Before validating code adherence to spec, you need a spec template defining a Files to Create/Modify section, which serves as the allowed list for validating file modifications.

Are there limitations to validating code scope by flagging modified files?▼

A limitation of validating code scope by flagging modified files is that it strictly enforces the allowed file list, meaning any necessary unlisted modifications will be flagged as violations.

Related Skills

Explore More Software Engineering Skills→
TestAny-ioTestAny-io
79

brd-interviewer

Guide phase-based interviews to convert business ideas into a BRD draft.

Official
Advanced
OzeroHAXOzeroHAX
32

review-code-requirements

Review pull requests for requirement traceability and scope compliance.

Community
Intermediate
sethvoltzsethvoltz
12

review

Review code diffs against repository standards and originating specifications.

Community
Advanced
Clouder0Clouder0

file-boundaries

Enforce file ownership boundaries to prevent conflicts during parallel development.

Community
Intermediate