ln-630-test-auditor

Coordinate six workers to audit automated and manual tests into a unified report.

Updated Mar 14, 2026

Search Tags:#automation #testing #documentation #audit #orchestration #quality-assurance

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-630-test-auditor-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-630-test-auditor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-630-test-auditor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-630-test-auditor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating comprehensive test-suite audits across automated and manual tests is complex and error-prone. This Skill centralizes orchestration, ensures consistent coverage, and produces a unified doc at docs/project/test_audit.md.

Core Features & Use Cases

Orchestrates six specialized workers to audit tests across 7 quality categories: Business Logic, E2E, Value, Coverage, Isolation, Manual Quality.
Generates a consolidated report and scores, writing to docs/project/test_audit.md.
Identifies missing tests, anti-patterns, and quality gaps to improve overall test health.

Quick Start

Run ln-630 to initiate the audit and generate docs/project/test_audit.md.

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 coordinate an audit across automated and manual test suites?▼

A multi-worker test suite audit orchestrates automated and manual test analysis by delegating tasks to specialized workers. This centralizes the process, ensures consistent coverage across quality categories, and aggregates findings into a unified report.

What is risk-based testing and how does it apply to test suite audits?▼

Risk-based testing patterns apply to test suite audits by prioritizing the analysis of test coverage based on potential domain-specific risks. This approach delivers a comprehensive compliance view and surfaces actionable advisories for critical gaps and anti-patterns.

How do I identify missing tests and anti-patterns in my test suite?▼

To identify missing tests and anti-patterns, orchestrate an audit across quality categories like Business Logic, E2E, Coverage, and Isolation. Specialized workers analyze the tests to detect quality gaps and surface actionable advisories for overall test health.

Can I generate a consolidated test audit report in markdown?▼

Yes, you can generate a consolidated test audit report directly to docs/project/test_audit.md. The orchestration process aggregates findings from multiple specialized workers to write comprehensive scores and a domain-agnostic compliance view into the markdown file.

What quality categories are covered during a comprehensive test audit?▼

A comprehensive test audit covers seven quality categories: Business Logic, E2E, Value, Coverage, Isolation, and Manual Quality. Specialized workers evaluate each category to identify anti-patterns and produce a unified compliance report.

Does the test audit orchestration require external dependencies?▼

No external dependencies are required to run the test audit orchestration. The process leverages internal specialized workers alongside MCP Context7 guidance to execute risk-based testing patterns and generate the final audit documentation.