Agent skill · Testing & QA

test-guard

Review generated or changed test code against universal testing rules before it ships or is presented for approval.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill test-guard --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 8 KB
Bundled scripts: none
Declared author: community
Path: skills/test-guard/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Test Guard You are reviewing generated or changed test code before it ships. Enforce the rules below after the first test-writing pass and before the tests are presented, committed, or merged. Be a sharp reviewer, not a pedantic one: flag what wastes maintenance effort or hides real bugs, ignore cosmetic preferences. These rules exist because coding agents over-generate tests. The common failure modes: mock-heavy unit tests that assert implementation details, near-duplicate test bodies that differ by one value, and tests that re-verify the framework instead of the project's logic. Each looks productive in a diff and costs maintenance forever. ## When to Use Use this skill when reviewing generated or changed test code before it ships. Activate it reactively after an agent writes, edits, generates, or refactors tests — unit tests, integration tests, e2e tests, or snapshot tests in any framework. ## When this skill activates - A coding agent has just written new test functions or test files, in any language - You are editing existing tests - You are reviewing a diff that contains test changes - The user asks you to write, add, or review tests ## Adapt to the project first These rule

What's inside
Steps it walks through
  1. When to Use
  2. When this skill activates
  3. Adapt to the project first
  4. What to do
  5. The Nine Rules
  6. Rule 1: Test behavior, not implementation
  7. Rule 2: Every mock must be justified
  8. Rule 3: One scenario per test, data-driven for variants
  9. Rule 4: Every test must justify its existence
  10. Rule 5: Name tests for the scenario
  11. Rule 6: Production regression tests are sacred
  12. Rule 7: No tests for framework guarantees
  13. Rule 8: State and value objects are real, never mocked
  14. Rule 9: Infrastructure under test gets real infrastructure
Ships with 4 files
  • references/jest.md
  • references/llm-app-testing.md
  • references/phpunit.md
  • references/pytest.md
More from agentic-awesome-skills
All skills →
About this skill
What does the test-guard skill do?

Review generated or changed test code against universal testing rules before it ships or is presented for approval.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill test-guard --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going