llm-artifacts-detection

# LLM Artifacts Detection Detect and flag common patterns introduced by LLM coding agents that reduce code quality. ## Detection Categories | Category | Reference | Key Issues | |----------|-----------|------------| | Tests | [references/tests-criteria.md](references/tests-criteria.md) | DRY violations, library testing, mock boundaries | | Dead Code | [references/dead-code-criteria.md](references/dead-code-criteria.md) | Unused code, TODO/FIXME, backwards compat cruft | | Abstraction | [references/abstraction-criteria.md](references/abstraction-criteria.md) | Over-abstraction, copy-paste drift, over-configuration | | Style | [references/style-criteria.md](references/style-criteria.md) | Obvious comments, defensive overkill, unnecessary types | ## Agent Prompts Use these prompts to spawn focused detection agents: ### Tests Agent ``` Analyze the test files for LLM-introduced test quality issues: 1. **DRY Violations**: Look for setup/teardown code repeated across multiple test functions instead of using fixtures or shared helpers. Flag patterns like: - Identical object creation in multiple tests - Repeated mock configurations - Copy-pasted database setup 2. **Library Testing**: Identify tests that validate standard library or framework behavior rather than application code. Signs: - No imports from the application codebase - Testing built-in functions or third-party library methods - Assertions about stdlib behavior 3. **Mock Boundaries**: Flag mockin...