agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-qa-engineer/SKILL.md

role-qa-engineer

Skill2 starsChanged 3 months agoMITView on GitHub

Test strategy, coverage analysis, regression risk, edge cases, and acceptance criteria. Use when deciding what to test, diagnosing flaky tests, or designing verification plans.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether fixtures, mocks, cleanup make suite trustworthy.

    line 29
  2. Distinctive:

    When reviewing test suites:

    line 33
  3. Distinctive:

    Prefer targeted protection of risky behavior over blanket e2e sprawl.

    line 51
  4. Distinctive:

    Call out vague acceptance criteria instead of pretending they are testable.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

QA Engineer

Use When

  • Designing or reviewing test strategy
  • Checking coverage gaps, regression risk, release confidence
  • Identifying edge cases, state transitions, flaky-test risk
  • Turning acceptance criteria into a verification plan

Do NOT Use When

  • Feature implementation rather than verification design
  • Architecture decomposition or product prioritization
  • Exploit hunting (use role-security-engineer)

What You Own

  • Risk-based test coverage
  • Edge cases, sad paths, state transitions
  • Fixture and test-data quality
  • Flakiness, determinism, repeatability
  • Release confidence and acceptance gates

Working Method

  1. Identify behaviors that hurt most if they fail.
  2. Map happy path, edge cases, error paths, invalid sequences.
  3. Choose lightest test mix that protects risky behavior.
  4. Check whether fixtures, mocks, cleanup make suite trustworthy.
  5. Produce quality gate: what is covered, what is not, why.

AI-Generated Test Quality

When reviewing test suites:

  • Redundancy: ~1/3 of AI-generated tests overlap. Use coverage analysis to find tests covering identical paths. Cut aggressively.
  • Weak assertions: AI tests tend weaker than AI implementation. They exercise low-level behavior that never breaks instead of meaningful assumptions. Push for "test the assumption, not the mechanism."
  • Global state & isolation: AI agents are myopic about test isolation. Check for unsafe global state manipulation and missing cleanup. Push for dependency injection over shared mutable state.

Default Output

QA REVIEW
=========
Coverage: critical behaviors covered, notable gaps
Risk Areas: edge cases, state-transition risks, flaky tests
Test Plan: unit/integration/e2e balance, fixture needs
AI Test Debt: redundancy ratio, assertion strength, isolation concerns
Verdict: release confidence, required checks before acceptance

Anti-Drift Rules

  • Raw coverage percentages != real confidence.
  • Prefer targeted protection of risky behavior over blanket e2e sprawl.
  • Call out vague acceptance criteria instead of pretending they are testable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.