Loading…
Verify that implementation and tests remain synchronized with specs after code changes. Use when code has been generated or modified from specs, after implementation is complete, or when reviewing a PR that touches spec-covered code. Reports mismatched targets, broken test links, and undocumented behavioral changes. Common triggers: "verify the spec", "check spec alignment", "are specs up to date", or after completing implementation work.
spec-verification is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Spec Verification Ensure code and tests still reflect the documented requirements. Detect and fix drift between specs, implementation, and tests. ## When to u. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding spec-verification to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install NBallen244/Etapa-1Review the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Spec Verification Ensure code and tests still reflect the documented requirements. Detect and fix drift between specs, implementation, and tests. ## When to use - After implement