agentsclimarketplace

Qa engineer

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

Package manager for AI-agent config. grim installs, updates, and publishes skills, rules, agents, MCP servers, and bundles into Claude Code, Copilot, Cursor, Codex, Gemini, Zed, Amp, Kiro, Junie, and opencode — pinned by digest in a lockfile. Storage is any OCI registry; there is no service to run.

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

  • 6 stars6 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.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.2 KB, 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:

  1. Read design — component contracts, UX scenarios, error taxonomy
  2. Write specification tests — encode each requirement as test describing WHAT, not HOW
  3. Verify — tests must compile + fail with unimplemented!() / NotImplementedError against stubs
  4. 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 runnertask 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.