ln-630-test-auditor

Name: ln-630-test-auditor
Availability: InStock
Author: cbbkrd-tech

Audit test suites across business logic, E2E coverage, and anti-patterns.

Updated Mar 9, 2026

Search Tags:#code quality #automation #testing #e2e #audit #coverage #domain-aware

Ready to run

npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-630-test-auditor-cbbkrd-tech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-630-test-auditor
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-630-test-auditor
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-630-test-auditor-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the comprehensive auditing of test suites, identifying areas for improvement in business logic coverage, E2E priority, test value, isolation, and adherence to best practices, ultimately leading to more robust and efficient testing.

Core Features & Use Cases

Automated Test Auditing: Analyzes test files against multiple quality dimensions.
Domain-Aware Coverage: Detects project domains and assesses test coverage specific to each.
Use Case: A development team can use this Skill to regularly audit their test suite, ensuring critical business logic is well-tested, low-value tests are removed, and E2E tests focus on essential user flows, all while identifying and flagging anti-patterns.

Quick Start

Run the ln-630-test-auditor skill to audit the current project's test suite.

Frequently Asked Questions about ln-630-test-auditor

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

FAQPage Schema

How do I audit my test suite for quality and coverage gaps?▼

To audit a test suite for quality and coverage, this tool orchestrates specialized workers to evaluate business logic, E2E priority, test value, isolation, and anti-patterns, then aggregates findings into a unified report.

What is domain-aware test coverage analysis?▼

Domain-aware test coverage analysis auto-detects project domains to perform targeted gap analysis, ensuring test coverage is evaluated specific to each domain's business logic and E2E user flows.

How do I identify low-value tests and anti-patterns in my codebase?▼

Identifying low-value tests and anti-patterns is handled by analyzing test files against multiple quality dimensions, flagging isolation issues and test value for removal or refactoring.

Can I use automated test auditing for E2E coverage priority checks?▼

Yes, automated test auditing evaluates E2E coverage priority by checking that end-to-end tests focus on essential user flows rather than redundant paths, improving testing efficiency.

Does the test audit report integrate with task tracking systems?▼

Yes, the test audit report integrates with task tracking by aggregating findings and creating a Linear task in Epic 0, directly linking coverage gap analysis to actionable work items.

What are the limitations of automated test suite auditing?▼

Limitations of automated test suite auditing include relying on auto-detected project domains for accurate coverage gap analysis, meaning highly unconventional project structures may affect targeted domain evaluation results.