skills.rest
amauryconstant
amauryconstantCOMMUNITY
Explore all skills by this author →
GitHub

osx-review-test-compliance

Map spec scenarios to test implementations and surface coverage gaps.

6|1|Updated Feb 12, 2026
Search Tags:#testing#test-coverage#gap-analysis#spec-analysis#orphaned-tests
One-click install
npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-review-test-compliance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: osx-review-test-compliance
Source: https://github.com/amauryconstant/openspec-extended/tree/main/resources/claude/skills/osx-review-test-compliance
Command: npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-review-test-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map spec scenarios to test implementations and surface coverage gaps across changes.

Core Features & Use Cases

  • Align spec-defined scenarios with existing tests to quantify coverage
  • Identify missing tests, orphaned tests, and propose targeted remediation
  • Support post-implementation reviews, PR audits, and ongoing quality assurance

Quick Start

Provide a focused, example-driven initiation to assess spec-to-test alignment for a given change.

Frequently Asked Questions about osx-review-test-compliance

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

FAQPage Schema
How do I analyze spec-to-test alignment and find missing test coverage?▼

Spec-to-test alignment maps spec scenarios to existing test implementations to quantify coverage. It identifies missing tests and orphaned tests, returning a structured gap-analysis summary with targeted remediation for post-implementation reviews.

What is an orphaned test and how do I identify it during code review?▼

An orphaned test is a test implementation lacking a corresponding spec scenario. Gap-analysis identifies orphaned tests by mapping spec scenarios to existing tests and surfacing coverage gaps across code changes during QA and PR audits.

How do I map spec scenarios to test implementations for gap analysis?▼

To map spec scenarios, provide focused example-driven inputs to compare defined scenarios against existing tests. This quantifies coverage and returns a structured summary proposing targeted remediation for missing or orphaned tests.

When do I need to perform spec-to-test gap analysis?▼

You need spec-to-test gap analysis after implementation, during code review, and for ongoing quality assurance. It verifies alignment between specs and tests across changes to ensure missing or orphaned tests are identified and remediated.

What is the best way to surface test coverage gaps across code changes?▼

The best way to surface test coverage gaps is mapping spec-defined scenarios with existing tests to quantify coverage. This structured gap-analysis identifies missing and orphaned tests, proposing targeted remediation for PR audits and QA.

Does gap analysis work for post-implementation reviews and PR audits?▼

Yes, gap analysis supports post-implementation reviews and PR audits by verifying alignment between specs and tests. It surfaces missing tests and orphaned tests across changes, returning actionable remediation for ongoing quality assurance.

Related Skills

Explore More Software Engineering Skills→
berkcangumusisikberkcangumusisik
11

test-coverage

Parse coverage reports and generate test scaffolds for untested code areas.

Community
Intermediate
jmaglyjmagly
175

test-sync

Detect orphaned tests and test-code misalignment between test suites and source code.

Community
Advanced
xxihxxih
1

springboot-verification

Validate Spring Boot applications with build, static analysis, coverage, and security scans.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

calculate-coverage

Measure code coverage percentage and identify untested code paths with pytest.

Official
Basic