speckit-version-guard-check

Verifies locked dependency versions and writes compatibility rules for downstream planning and implementation.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-version-guard-check-kamijeong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-version-guard-check
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-version-guard-check
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-version-guard-check-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies locked dependency versions against live npm registries so teams can catch outdated stacks, compatibility risks, and security concerns before generating plans or implementation work.

Core Features & Use Cases

  • Version verification: Compares resolved package versions from lockfiles or package manifests with the latest stable releases.
  • Risk detection: Checks for known issues, advisories, and version mismatches that could affect downstream coding tasks.
  • Migration guidance: Produces compatibility rules and upgrade notes for packages that are behind current releases.
  • Use Case: A developer preparing a feature branch can run this Skill first to ensure generated code follows the correct APIs for the currently locked dependencies.

Quick Start

Ask the skill to inspect the repository’s dependency sources and generate a version guard report for the current project.

Frequently Asked Questions about speckit-version-guard-check

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

FAQPage Schema
How do I check npm dependency versions against live registries before generating code?

Dependency version verification compares resolved package versions from lockfiles or package manifests with the latest stable releases to catch compatibility risks. It checks locked dependencies against live npm registries to ensure generated code follows correct APIs.

How do I detect security advisories and version mismatches in a spec-kit project?

Detect security advisories by checking known issues across lockfiles and package manifests. The process performs vulnerability lookups and risk detection to identify outdated stacks and version mismatches that could affect downstream coding tasks.

Does this dependency audit work with lockfiles and package manifests?

Yes, the dependency audit works with lockfiles, package manifests, and decision records. It inspects these sources to verify locked dependency versions and applies to spec-kit projects needing package status checks before code generation.

What is the best way to generate compatibility rules for outdated npm packages?

Generate compatibility rules by collecting migration references and producing reports with mandatory constraints. This creates upgrade notes for packages behind current releases, guiding downstream planning and implementation with verified compatibility rules.

Why does version verification matter before starting a feature branch?

Version verification matters because it ensures generated code follows correct APIs for currently locked dependencies. Running checks before feature branch work prevents compatibility risks and security concerns from affecting downstream implementation tasks.