hf.audit-integration-tests

Audit integration test coverage across modules for gaps and anti-patterns.

5|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/T-rav/hydraflow --skill hf-audit-integration-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf.audit-integration-tests
Source: https://github.com/T-rav/hydraflow/tree/main/.codex/skills/hf.audit-integration-tests
Command: npx skills add https://github.com/T-rav/hydraflow --skill hf-audit-integration-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integration tests across modules are often fragmented, leaving gaps that allow regressions when components interact.

Core Features & Use Cases

  • Automatically scan test suites to assess cross-module coverage and surface integration gaps.
  • Detect anti-patterns in tests (false integration tests, duplicated fixtures, excessive mocks) and suggest remediation.
  • Generate grouped GitHub Issues by theme to consolidate findings and drive targeted improvements.

Quick Start

Run the audit workflow to begin identifying cross-module integration gaps and anti-patterns.

Frequently Asked Questions about hf.audit-integration-tests

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

FAQPage Schema
How do I audit integration test coverage across multiple modules?

To audit integration test coverage, the Skill scans test files for integration marks, fixtures, and cross-module calls to map coverage and surface potential gaps. It outputs structured findings aligned with repository targets.

What are common anti-patterns in pytest integration tests?

Common integration test anti-patterns include false integration tests, duplicated fixtures, and excessive mocks. The audit detects these issues and suggests targeted remediations to harden cross-module interactions.

How do I generate GitHub Issues for testing gaps automatically?

You can generate grouped GitHub Issues for testing gaps by running the audit workflow. It consolidates findings into themed issues to drive targeted improvements and align with issue tracking.

Why do my components regress even with existing integration tests?

Components regress because integration tests across modules are often fragmented, leaving coverage gaps. The audit identifies missing cross-module interactions to prevent future component regressions.

Can I scan test suites to find duplicated fixtures without extra dependencies?

Yes, you can scan test suites to find duplicated fixtures without extra dependencies. The Skill operates independently to analyze test files and detect anti-patterns like excessive mocks and duplicated fixtures.