opsx-coverage-scan

Audit legacy PHP and frontend codebases against OpenSpec requirements using git history analysis.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill opsx-coverage-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-coverage-scan
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/opsx-coverage-scan
Command: npx skills add https://github.com/ConductionNL/shillinq --skill opsx-coverage-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the "retrofit gap" in legacy applications by identifying which parts of the codebase implement specific OpenSpec requirements and which requirements remain unimplemented or broken.

Core Features & Use Cases

  • Automated Coverage Mapping: Automatically buckets code units into six categories based on their alignment with OpenSpec requirements.
  • Git-History Analysis: Uses a high-performance reverse-pass to detect if requirements were previously implemented but subsequently removed.
  • ADR Conformance: Performs a sweep for architectural compliance, including missing spec tags and forbidden patterns.
  • Use Case: Before starting a major refactor, run this scan to generate a comprehensive coverage report that tells you exactly which files need annotation and which requirements are missing implementation.

Quick Start

Run the opsx-coverage-scan skill for the procest application to generate a full coverage report.

Frequently Asked Questions about opsx-coverage-scan

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

FAQPage Schema
How do I audit legacy code against OpenSpec requirements for compliance?

To audit legacy code against OpenSpec requirements, this Skill maps implementation units to spec criteria using heuristic classification and git history analysis. It generates coverage reports and parseable JSON sidecars to identify unimplemented or broken requirements.

What is the best way to trace retrofit coverage gaps in a PHP codebase?

Tracing retrofit coverage gaps in a PHP codebase involves bucketing code units into alignment categories and running a reverse-pass git history analysis. This process detects previously removed requirements and produces a comprehensive coverage report for retrofit planning.

Can I verify architectural conformance and detect missing spec tags automatically?

You can verify architectural conformance automatically by performing a sweep for missing spec tags and forbidden patterns. This ADR conformance check identifies compliance violations across legacy application codebases to ensure spec-to-code traceability.

Does the coverage scan work with both PHP and frontend codebases?

Yes, the coverage scan operates on both PHP and frontend codebases. It audits legacy application code by mapping implementation units against OpenSpec requirements to produce coverage reports and parseable JSON sidecars.

How do I generate a coverage report to identify which files need annotation before a refactor?

To generate a coverage report before a refactor, run the scan to map your codebase against OpenSpec requirements. The resulting report identifies exactly which files require annotation and which requirements are missing implementation.

What are the limitations of using heuristic classification for spec-to-code traceability?

Using heuristic classification for spec-to-code traceability relies on pattern matching rather than strict execution tracing, which may produce approximations. It is limited to detecting spec tags, forbidden patterns, and git history removals without deep runtime behavioral analysis.