test-classification

To automatically classify test files by type, you can target a specific directory to categorize tests as unit, integration, or e2e based on filename patterns and content validation, flagging those needing deep analysis.

Mock detection works by evaluating content signals within test files to identify heavy mocking or mocking of core modules, flagging potential violations in unit tests that require further inspection.

The best way to triage integration tests is to scan for integration test characteristics and mock appropriateness, flagging files that require deeper analysis so developers can focus review efforts efficiently.

You need AST verification lines for precise line counting during a test audit when available, ensuring accurate categorization and risk detection within the target directory.

You cannot rely solely on filename patterns to categorize tests; the classification also requires content validation and risk detection to accurately identify test types and potential mock violations.

The test-classification skill flags certain unit tests for deep analysis because it detects suspicious mock usage, such as heavy mocking or mocking of core modules, indicating potential violations that need manual review.