Skip to content
Skills Library
Programming · Testing

grill-testing

/grill-testing

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.

Licence
ISC
Last repository change
02.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.

Licence

ISC, otwarta.

What it does and when to use it

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.

Original author 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.

How it works

  1. Analysis Areas
Original SKILL.md headings · 45 lines, 335 words
SKILL.md preview
---
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
---

# Grill Testing

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.

## Analysis Areas

### 1. Test Coverage & Gaps
- What percentage of the codebase has tests? (estimate by counting test files vs source files)
- Which critical paths are untested?
- Which modules have good coverage vs none?
- Are edge cases and error paths tested?

**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.

### 2. Test Quality
- Are tests testing behavior or implementation details?
- Test isolation: do tests depend on each other or external state?
- Test naming: can you understand what failed from the test name?
- Assertion quality: meaningful assertions vs just "doesn't throw"
- Flaky test indicators (timeouts, retries, sleep/wait in tests)
- Test doubles: appropriate use of mocks/stubs vs over-mocking

### 3. Test Infrastructure
- Test framework and runner setup
- Test fixtures and factories — reusable or copy-pasted?
- Database/service setup for integration tests
- Snapshot testing: appropriate use or snapshot bloat?
- Performance/load tests present?

### 4. CI/CD Pipeline
- Pipeline stages and what they run
- Build times (if inferable from config)
- Deployment strategy (manual, CD, canary, blue-green)
- Environment parity (does CI match production?)
- Missing pipeline stages (linting, type checking, security scanning)

**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."

Versions

The database has no other skills named grill-testing.

Database snapshot: 13.11.2026 · package version 417311266ff2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90grill-error-handling
    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.
  • 90test-coverage-analyzer
    Automated test coverage analysis with support for multiple testing frameworks, coverage reporting, gap identification, metric tracking, and quality gate enforcement. Use when Claude needs to analyze test coverage, identify untested code, generate coverage reports, or enforce…
  • 100test-coverage-guardian
    Analyze test coverage, identify gaps, detect dead code, and improve test quality. Use when user asks to check coverage, review tests, find untested code, or improve test robustness.
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100grill-me-qa
    A guided interview to challenge and validate QA automation plans, test strategies, and framework designs before implementation. Use when the user wants to validate a test architecture, challenge a testing decision, prepare an AI-assisted testing rollout, or uses any "grill"…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.