skills.rest
BellaBe
BellaBeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-coverage

Trace spec items to build definitions and generated code in YAML coverage reports.

37|5|Updated Nov 18, 2025
Search Tags:#verification#traceability#coverage#gaps
One-click install
npx skills add https://github.com/BellaBe/lean-os --skill verify-coverage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-coverage
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/engineering-verify-coverage
Command: npx skills add https://github.com/BellaBe/lean-os --skill verify-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures complete traceability from spec to build to generated code, surfacing gaps in coverage.

Core Features & Use Cases

  • Traceability matrix: map spec objects/morphisms/effects to build outputs.
  • Gaps detection: identify missing traces and provide remediation.
  • Coverage report: produce artifacts/v{N}/verify/coverage-report.yaml.

Quick Start

Example: "Run coverage check for artifacts/v1/spec/.yaml against artifacts/v1/build/.yaml."

Frequently Asked Questions about verify-coverage

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

FAQPage Schema
How do I verify traceability from specification to generated code?▼

Traceability verification maps spec objects, morphisms, and effects through build definitions to generated code, calculating coverage percentage and surfacing gaps. Run coverage check against artifacts/v{N}/spec, build, and gen directories to produce a detailed YAML report.

What does a coverage report show and where is it stored?▼

The coverage report outputs to artifacts/v{N}/verify/coverage-report.yaml, detailing traced items, unmapped spec-to-build and build-to-code connections, completion percentage, and remediation guidance for gaps across all enabled targets.

Can I detect missing traces between my spec and build artifacts?▼

Yes. The Skill identifies gaps in traceability by collecting spec items, tracing them to build definitions, and reporting which objects, morphisms, effects, and constraints lack complete mappings, enabling you to close coverage holes.

What artifacts and file formats does the coverage check validate?▼

Coverage validation works across YAML spec files, build definitions, and generated code within versioned artifact directories (artifacts/v{N}), tracing objects, morphisms, effects, and constraints across all three layers.

How is coverage percentage calculated across spec, build, and generated code?▼

Coverage percentage is calculated by counting successfully traced items at each stage—spec-to-build mappings and build-to-code mappings—against total items defined, expressing completeness as a percentage in the final report.

Related Skills

Explore More Software Engineering Skills→
BellaBeBellaBe
37

gen-maps

Generate verifiable YAML code maps for operations, handlers, and repositories.

Community
Advanced
ref-docsref-docs

traceability-auditor

Validate end-to-end traceability across requirements, design, tasks, code, and tests.

Official
Advanced
BellaBeBellaBe
37

foundation-schema

Validate LeanOS artifact manifests in artifacts/vN/ against foundation-schema definitions and cross-references.

Community
Advanced
nesquikmnesquikm
6

spec-review

Audit code implementations against formal specifications to reveal deviations and gaps.

Community
Advanced