Oldhand QA
Runs the QA panel for a change: turns the contract's acceptance and regression criteria into scenario cards (acceptance, the original failing case, neighbouring regressions, negative paths and messy real-world input), spawns one QA sub-agent per scenario to drive the real app through a browser, computer use, an API or a CLI, collects screenshots and response bodies as evidence, tallies pass, fail and blocked into the task ledger, and has the lead re-run the most important scenario itself. Use when the user says "QA this change", "run the QA scenarios", "make sure existing stuff still works", "
Install
/plugin marketplace add berwinsingh/oldhandThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add berwinsingh/oldhand --skill oldhand-qagit clone --depth 1 https://github.com/berwinsingh/oldhand.git /tmp/oldhand
mkdir -p ~/.claude/skills
cp -r /tmp/oldhand/skills/oldhand-qa ~/.claude/skills/oldhand-qaPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# oldhand-qa
The panel. Every scenario gets its own QA sub-agent that starts at the real entry point, drives the real
app and brings back evidence. You write the scenarios, run the panel, then check its work yourself: an
agent's PASS is evidence, never verification.
## What the user typed
`$ARGUMENTS` (other hosts: the text after the skill name): a task, an environment, scenario ids or `--quick`.
## Reads and writes
Reads `contract.md` (criteria, mode, environments, authorized actions), `plan.md`, `rca.md` and
`ledger.json`. Writes only under `.oldhand/<task>/qa/` plus ledger records, never the source tree.
`D` is the task folder. Tools: QA is `python3 "${CLAUDE_SKILL_DIR}/scripts/qa.py"` and LEDGER is
`python3 "${CLAUDE_SKILL_DIR}/../oldhand/scripts/ledger.py"`; run their commands one at a time. If
that variable is not expanded on your host, use this skill's own folder. If ledger.py is not at
that path, the pack is only partly installed: tell the user to install all 11 skills and stop.
Plan-only mode: do Steps 1 to 3 and stop; spawn nothing, drive nothing, and let oldhand-plan carry the
scenario list. Verify mode: run every step and fix nothing.
## Step 1: Find the task
`D` is the task folder the conversation names (`Task folder: <path>`), else the one `LEDGER where`
prints. None, or a contract about another request: run the oldhand-contract steps in short form:
`LEDGER init --dir .oldhand/<task> --title "<t>" --mode verify`, write `contract.md` with 2 to 6 linesDetails
- Skill name
oldhand-qa- Repository
- berwinsingh/oldhand
- Path
skills/oldhand-qa/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Oldhand QA skill do?
Runs the QA panel for a change: turns the contract's acceptance and regression criteria into scenario cards (acceptance, the original failing case, neighbouring regressions, negative paths and messy real-world input), spawns one QA sub-agent per scenario to drive the real app through a browser, computer use, an API or a CLI, collects screenshots and response bodies as evidence, tallies pass, fail and blocked into the task ledger, and has the lead re-run the most important scenario itself. Use when the user says "QA this change", "run the QA scenarios", "make sure existing stuff still works", "
How do I install the Oldhand QA skill?
Claude Code plugin: /plugin marketplace add berwinsingh/oldhand. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Oldhand QA popular?
It lives in berwinsingh/oldhand, which has 9 GitHub stars and 2 forks.
Related skills
Oldhand
9berwinsingh/oldhand
Conducts non-trivial software work end to end through a chain of stage skills: reads the ticket or prompt, traces the real code path, reuses proven code, makes the smallest correct change, has sub-agents review and QA it in the running app, and lets a computed verdict, not the model, say when it is done. Use when the user asks to implement, build, fix, debug, root-cause, investigate, QA or verify a feature or bug; says "pick up this ticket", "work on ENG-123", "fix this bug", "why is X broken", "plan this first" or "make sure it works end to end"; or pastes a Jira, Linear, Asana, monday.com or
Oldhand Build
9berwinsingh/oldhand
Implements a planned change the lazy, correct way: reuse what the codebase has, then the standard library, the platform and installed dependencies, and only then the least new code, fixing the whole class of bug at the shared point. Takes a baseline of the repo checks before the first edit, leaves one focused regression check, proves that check guards the fix with a mutation run (mutate.py), and compares the checks with the baseline. Records unit, integration and mutation results in the Oldhand ledger and writes build.md in the task's .oldhand folder. Use when the user says "implement the plan
Oldhand Contract
9berwinsingh/oldhand
Turns a ticket, document or prompt into a work contract with numbered acceptance criteria (AC) and regression criteria (R), then opens the task's .oldhand folder and ledger that every later Oldhand stage reads. Reads the whole tracker item (description, every comment, attachments, linked work), keeps the user's assumptions, changed requirements, constraints, partial work and requested proof, and records which remote actions are authorized. Use when the user says "here is the spec", "scope this", "write the acceptance criteria" or "what exactly is being asked". Not for one-line edits, typo fixe
Rxmembersim
9mark64oswald/healthsim-workspace
RxMemberSim generates realistic synthetic pharmacy data for testing PBM systems, claims adjudication, and drug utilization review. Use when user requests: (1) pharmacy claims or prescription data, (2) DUR alerts or drug interactions, (3) formulary or tier cohorts, (4) pharmacy prior authorization, (5) NCPDP formatted output.
Membersim
9mark64oswald/healthsim-workspace
MemberSim generates realistic synthetic claims and payer data for testing claims processing systems, payment integrity, and benefits administration.
Amz Product Optimizer
9simoncai519/open-accio-skill
Use when user wants to optimize Amazon product listings, generate product images, improve titles, monitor CTR, or automate end-to-end Amazon product optimization workflows.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.