speckit-version-guard-validate

Scan modified source files for API patterns conflicting with locked dependency versions.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-version-guard-validate-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-version-guard-validate
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-version-guard-validate
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-version-guard-validate-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch API usage that conflicts with locked dependency versions before it turns into a broken build, failed runtime, or blocked release.

Core Features & Use Cases

  • Compatibility Validation: Scans changed source files for patterns that violate version rules documented in the project report.
  • Advisory Reporting: Surfaces each finding with the file, line number, incompatible pattern, and the version-correct replacement.
  • Resilient Workflow Handling: Falls back to alternate report sources, scans broadly when changed files are unavailable, and continues even when some lookups fail.
  • Use Case: A developer finishes an implementation and wants a fast post-check that flags React, Python, or framework APIs that do not match the repo’s pinned dependency versions.

Quick Start

Use this Skill to review the implementation changes in the current project and report any version-incompatible API patterns with their recommended replacements.

Frequently Asked Questions about speckit-version-guard-validate

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

FAQPage Schema
How do I validate API patterns against locked dependency versions before shipping?

Version conflict scanning checks modified source files for API patterns that violate rules documented in your project report, providing advisory reporting with file locations and version-correct replacements.

Does this work for FastAPI and frontend code changes in a Spec-Kit workflow?

It supports FastAPI, Python, and frontend or backend code changes within Spec-Kit workflows, applying extracted compatibility rules to validate post-implementation dependencies.

What happens if changed files are unavailable during post-implementation validation?

It provides resilient workflow handling by falling back to alternate report sources and scanning broadly when changed files are unavailable, continuing even when some lookups fail.

How do I find incompatible React or Python API usage in my modified source files?

Scanning changed source files against pinned dependency versions identifies incompatible React or Python API patterns, surfacing each finding with the file, line number, and the version-correct replacement.

Does dependency compatibility validation include security reminders for critical CVEs?

Advisory reporting during validation includes security reminders for critical or high CVEs, ensuring that version-incompatible API patterns and security vulnerabilities are both flagged.