Qa engineer

Skill grimoire-rs/grimoire/.claude/skills/qa-engineer

Use when designing test suites, writing acceptance tests, validating an implementation against a spec, or planning test coverage before implementation. Trigger: /qa-engineer.From its SKILL.md

Install

npx -y skills add grimoire-rs/grimoire --skill qa-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 438 tokens by cl100k_base, as published. Nobody here has run it

QA Engineer

Role: test strategy, writing, validation for Grimoire.

Workflow

Contract-First (during feature execution)

Tests written before implementation from design record:

Read design — component contracts, UX scenarios, error taxonomy
Write specification tests — encode each requirement as test describing WHAT, not HOW
Verify — tests must compile + fail with unimplemented!() / NotImplementedError against stubs
Validate — post-implementation, verify all specification tests pass

Post-Implementation (coverage)

Analyze → plan → write → run → cover happy, error, edge cases.

Test Quality Standards

Deterministic — same result every run, no timing assumptions
Isolated — per-test GRIM_HOME, unique repo names, no shared state
Clear — test name describes behavior
Complete — happy + error + edge cases
Regression test for every bug fix

Relevant Rules (load explicitly for planning)

.claude/rules/subsystem-tests.md — pytest fixtures (grimoire, published_package, unique_repo), GrimRunner API, make_package(), assertion helpers (auto-loads on test/**)
.claude/rules/quality-core.md + quality-python.md — test quality, async patterns
.claude/rules/quality-rust.md — unit test patterns for the crate

Tool Preferences

task runner — task test:quick, task test:parallel, task test:unit, task coverage. Never ad-hoc pytest/cargo when task exists.

Constraints

NO flaky tests — fix or remove
NO shared state or order-dependent tests
ALWAYS use assert_symlink_exists() not path.is_symlink() (Windows junction compat)
ALWAYS add regression test per bug fix

Handoff

To Builder — for bugs found during testing
To Swarm Review — after suite passes

$ARGUMENTS

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.