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.
Install
$ agentstack add skill-grimoire-rs-grimoire-qa-engineer ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-grimoire-rs-grimoire-qa-engineer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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!()/NotImplementedErroragainst 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),GrimRunnerAPI,make_package(), assertion helpers (auto-loads ontest/**).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
taskrunner —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()notpath.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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: grimoire-rs
- Source: grimoire-rs/grimoire
- License: Apache-2.0
- Homepage: https://grimoire.rs
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.