skills.rest
johan--
johan--COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-coverage-map

Generate ASCII diagrams and coverage statistics mapping specifications to code files.

1|Updated Jan 24, 2026
Search Tags:#code analysis#spec-driven development#reverse engineering#spec coverage#coverage mapping
One-click install
npx skills add https://github.com/johan--/stackshift --skill spec-coverage-map-johan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-coverage-map
Source: https://github.com/johan--/stackshift/tree/main/skills/spec-coverage-map
Command: npx skills add https://github.com/johan--/stackshift --skill spec-coverage-map-johan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers ensure comprehensive code coverage by mapping specifications to implementation files, identifying gaps, and analyzing shared resources.

Core Features & Use Cases

  • Spec-to-Code Mapping: Generates ASCII diagrams and reverse indexes to visualize the relationship between specifications and code files.
  • Coverage Statistics: Provides percentages by category (backend, frontend, infrastructure) and identifies gap files.
  • Shared Files Analysis: Highlights files referenced by multiple specs and assesses their risk level.
  • Use Case: After implementing features, use this Skill to validate spec coverage and ensure no important code is left untested.

Quick Start

Run the 'spec-coverage-map' skill to generate a spec-to-code coverage map for your project.

Frequently Asked Questions about spec-coverage-map

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

FAQPage Schema
How do I map specifications to implementation files in my codebase?▼

Spec-to-code coverage mapping works by generating ASCII diagrams and reverse indexes that show relationships between specifications and code files. It validates spec coverage after implementation by highlighting gaps and shared resources.

What is the best way to visualize spec coverage during code cleanup?▼

The best way to visualize spec coverage during code cleanup is to generate coverage statistics and ASCII diagrams. This highlights gap files, analyzes files referenced by multiple specs, and assesses their risk level for safe refactoring.

Can I identify gap files and untested code using spec-driven development?▼

Yes, you can identify gap files and untested code by generating coverage statistics grouped by category like backend, frontend, and infrastructure. This maps specifications to implementation files and highlights any important code left untested.

How do I generate coverage statistics by category for backend and frontend code?▼

Generate coverage statistics by category by running a spec-to-code coverage map. It provides percentages for backend, frontend, and infrastructure files, identifies gap files, and shows which specifications cover specific implementation files.

Does spec coverage mapping work for analyzing shared files referenced by multiple specs?▼

Yes, spec coverage mapping works for analyzing shared files referenced by multiple specs. It highlights these files and assesses their risk level, helping developers manage dependencies and prevent conflicts during spec-driven development.

Related Skills

Explore More Software Engineering Skills→
robikscuberobikscube

spec-splitter

Split construction project manual PDFs into CSI-formatted specification section files with extracted text.

Community
Advanced
jmaglyjmagly
175

test-coverage

Analyze lcov, cobertura, and istanbul coverage reports to identify gaps and recommend prioritized tests.

Community
Intermediate
nolanvenholanolanvenhola
3

symbol-sweep

Audit cross-file symbolic references and replace hardcoded operands in Zeliard TASM assembly source.

Community
Advanced
roberttmadsen13-delroberttmadsen13-del

Code Coverage with gcov

Instrument C/C++ builds with gcov and generate text and HTML coverage reports.

Community
Advanced