skills.rest
axiomantic
axiomanticOFFICIAL
Explore all skills by this author →
GitHub

auditing-green-mirage

Audit test suites against production code to expose coverage gaps.

8|5|Updated Dec 30, 2025
Search Tags:#audit#traceability#quality-assurance#test-suites#production-code#green-mirage
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill auditing-green-mirage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auditing-green-mirage
Source: https://github.com/axiomantic/spellbook/tree/main/skills/auditing-green-mirage
Command: npx skills add https://github.com/axiomantic/spellbook --skill auditing-green-mirage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing-green-mirage helps teams prove that their test suites actually exercise production code and catch real failures, rather than just reporting passing tests.

Core Features & Use Cases

  • End-to-end traceability from tests to production code, exposing gaps where broken behavior would slip through.
  • Evidence-based findings with exact line numbers, code snippets, and a structured remediation plan.
  • Machine-readable audit reports (YAML+markdown) plus a phase-driven remediation roadmap for PRs.

Quick Start

Provide your test suite and production code samples, then run an audit to generate the green-mirage report.

Frequently Asked Questions about auditing-green-mirage

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

FAQPage Schema
How do I audit a test suite to prove it actually verifies production code?▼

Auditing a test suite involves tracing tests to production code to expose gaps where broken behavior would slip through. This process generates evidence-based findings with exact line numbers and a dependency-ordered remediation plan.

What is a green mirage in test suites and how do I identify hidden test gaps?▼

A green mirage is a passing test suite that fails to verify correctness. You identify hidden test gaps by applying end-to-end traceability from tests to production code, documenting line-level evidence where broken code passes undetected.

How do I generate a machine-readable audit report for quality assurance findings?▼

You generate machine-readable audit reports by outputting YAML and markdown files. These reports include structured metadata, specific findings with line numbers, code snippets, and a phase-driven remediation roadmap for pull requests.

Can I apply test suite auditing to any production codebase?▼

You can apply test suite auditing to any test suite and its corresponding production code. The audit outputs line-level evidence, exact fixes, and a dependency-ordered remediation plan regardless of the codebase context.

What is the best way to create a dependency-ordered remediation plan for failing tests?▼

Creating a dependency-ordered remediation plan requires auditing test suites to document line-level evidence. This generates a phase-driven roadmap detailing exact fixes ordered by code dependencies for pull requests.

Related Skills

Explore More Software Engineering Skills→
ArdurAIArdurAI
1

god-dev-codebase

Automate codebase review, security audits, and performance analysis.

Official
Advanced
data-playersdata-players

he-dev

Convert software specifications and plans into ready-to-test code implementations.

Official
Advanced
wshaddixwshaddix
71

crap-analysis

Analyze .NET code for CRAP scores and generate coverage reports.

Community
Intermediate
copyleftdevcopyleftdev

lipton-mutation-testing

Inject faults into source code and calculate mutation scores for test suites.

Community
Advanced