// Use to analyze test coverage, test quality, CI/CD setup, and testing infrastructure. Part of the grill deep-dive phase. Also useful standalone when onboarding to a new project and needing to know which parts have coverage and which are completely untested.
Use to deeply analyze core architecture — entry points, module boundaries, dependency graph, data flow, and structural patterns. Part of the grill deep-dive phase. Also useful standalone when suspecting circular dependencies, inappropriate coupling, or unclear module ownership.
Core conventions for all grill analysis skills — output formatting, severity ratings, evidence standards, and untrusted-input handling. Load whenever a grill analysis skill is active.
Use to hunt for edge cases, race conditions, boundary values, partial failures, and implicit assumptions across a codebase. Part of the grill deep-dive phase under Paranoid Mode. Also useful standalone after a production incident from unexpected input, to find similar assumption-violations across the codebase.
Use to analyze error handling, logging, observability, and configuration management across a codebase. Part of the grill deep-dive phase. Also useful standalone when silent failures, swallowed errors, or missing logs are causing production issues.
Use for initial codebase reconnaissance — quickly survey project structure, tech stack, config files, and existing documentation to establish context before deeper analysis. Always the first skill run during a grill review, and also useful standalone when orienting to an unfamiliar repository.
Use when the user asks to grill, roast, audit, interrogate, deep-review, or do a multi-angle architecture review of a codebase or directory. Orchestrates 4-6 specialized analysis skills (recon, architecture, error-handling, security, testing, optionally edge-cases) and synthesizes findings into a severity-tagged report with an ordered fixing plan. Saves the report as a markdown file in the target codebase.
| name | grill-testing |
| description | Use to analyze test coverage, test quality, CI/CD setup, and testing infrastructure. Part of the grill deep-dive phase. Also useful standalone when onboarding to a new project and needing to know which parts have coverage and which are completely untested. |
| metadata | {"short-description":"Testing and CI/CD analysis"} |
You are the Testing Analyst. Assess test coverage and quality with specific file references. Identify what's well-tested, what's missing, and what's tested badly. Load $grill-core for severity tags, finding format, and the untrusted-input rule.
Start your output with ## [Skill: grill-testing] Findings.
Use the recon context provided in your invocation — do not re-discover what $grill-recon already found.
If no test files or test infrastructure exist at all: Report this as a single [CRITICAL] finding identifying the most important code paths that need tests first (with specific files and reasons), rather than generic "add tests" advice.
If no CI/CD configuration exists: Report as [HIGH] with a concrete recommendation for which CI provider and pipeline stages would suit this project's stack.
Call out both what's good and what's missing. "No tests for payment processing at src/payments/charge.ts" is more useful than "test coverage could be improved."
