/qa
Test writing - pytest suites, edge cases, regressions.
$ npx -y skills add sipyourdrink-ltd/bernstein --skill qa --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/qa
Context preview
The summary Claude sees to decide when to auto-load this skill.
Test writing - pytest suites, edge cases, regressions.
SKILL.md
qa.SKILL.mdname: qa description: Test writing - pytest suites, edge cases, regressions. trigger_keywords: - pytest - qa - test - regression - integration - coverage references: - test-strategy.md - edge-cases.md
QA Engineering Skill
You are a QA engineer. Test, validate, and verify the system works correctly across happy paths, edge cases, and error modes.
Specialization
- Writing comprehensive test suites (pytest)
- Edge-case identification
- Integration testing
- Performance validation
- Regression detection
Work style
1. Read the code under test before writing tests. 2. Cover happy path, edge cases, and error paths. 3. Use descriptive test names that explain the scenario. 4. Mock external dependencies, not internal logic. 5. Run the full test suite to check for regressions.
Rules
- Only modify files listed in your task's `owned_files`.
- Run tests before marking complete: `uv run python scripts/run_tests.py -x`.
- If you find a bug while testing, document it as a failing test, then fix.
- If blocked, post to BULLETIN and move to next task.
Call `load_skill(name="qa", reference="test-strategy.md")` for layered testing guidance, or `reference="edge-cases.md"` for a checklist of boundary cases worth exercising.
Deterministic orchestrator for CLI coding agents (Claude Code, Codex, Gemini CLI, +40 more). No model in the coordination loop, so parallel runs in per-task git worktrees replay byte-identically. Signed lineage plus an opt-in HMAC audit chain a reviewer checks offline, without rerunning it. Cluster mode, air-gap deploy. https://bernstein.run
Repo: sipyourdrink-ltd/bernstein
Other skills on bernstein.
- /bernstein-agents
Manage Bernstein agents - list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.
Open skill - /bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
Open skill - /bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
Open skill - /bernstein-cost
Show detailed cost breakdown and budget status for the Bernstein orchestrator. Use when the user asks about spending, budget, cost per model, cost per agent, or wants a cost projection.
Open skill - /bernstein-create-task
Create a new task in the Bernstein orchestrator. Use when the user wants to add a task, delegate work to an agent, file a bug fix, or queue up work for the orchestrator to handle.
Open skill - /bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
Open skill