Oldhand Review
Reviews a code change with a board of read-only reviewer sub-agents, one lens each (contract, correctness, security and simplicity, plus data and AI behaviour when the change touches them). Each reviewer reads a stand-alone brief and writes a memo of file:line findings with failure scenarios; the chair tries to refute every finding before accepting it, records survivors in the Oldhand ledger, fixes high and medium findings, and lists lows as follow-ups. One review round and one fix round. Writes review.md and a review folder in the task's .oldhand folder. Use when the user says "review this",
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-reviewgit clone --depth 1 https://github.com/berwinsingh/oldhand.git /tmp/oldhand
mkdir -p ~/.claude/skills
cp -r /tmp/oldhand/skills/oldhand-review ~/.claude/skills/oldhand-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# oldhand-review
The board. Each reviewer reads the change through one lens and sees neither the conversation nor the
other memos, so it cannot be talked into agreeing. The chair (the lead) keeps only findings that
survive an honest attempt to refute them: a made-up defect costs as much as a missed one.
## What the user typed
`$ARGUMENTS` (other hosts: the text after the skill name): a base branch, a PR, lenses to add or drop.
## Reads and writes
`LEDGER` means `python3 "${CLAUDE_SKILL_DIR}/../oldhand/scripts/ledger.py"`, `MUTATE` means
`python3 "${CLAUDE_SKILL_DIR}/../oldhand-build/scripts/mutate.py"`, and the lens file is
`${CLAUDE_SKILL_DIR}/lenses.md`; run their commands one at a time. If that variable is not expanded on your
host, use this skill's own folder and its siblings; if ledger.py is not there, the pack is only partly
installed: tell the user to install all 11 skills and stop. `D` is the task folder. Reads `contract.md`,
`plan.md`, `build.md`, `trace.md`, the diff. Writes `D/review/`, `D/review.md`, findings, fixes, records.
## Step 1: Load the task and the change
`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
--mode investigate`, `contract.md` with `Mode: investigate` and 2-6 lines like `- AC1: <outcome> (proof:Details
- Skill name
oldhand-review- Repository
- berwinsingh/oldhand
- Path
skills/oldhand-review/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Oldhand Review skill do?
Reviews a code change with a board of read-only reviewer sub-agents, one lens each (contract, correctness, security and simplicity, plus data and AI behaviour when the change touches them). Each reviewer reads a stand-alone brief and writes a memo of file:line findings with failure scenarios; the chair tries to refute every finding before accepting it, records survivors in the Oldhand ledger, fixes high and medium findings, and lists lows as follow-ups. One review round and one fix round. Writes review.md and a review folder in the task's .oldhand folder. Use when the user says "review this",
How do I install the Oldhand Review 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 Review 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
Adapty Docs
9adaptyteam/adapty-skills
Use when an Adapty question has no page already linked in the skill you are holding — how a product or dashboard feature behaves, what a setting does, a limit, store connections, Flow Builder, the Developer CLI, the server-side API, or an SDK method on any platform. Also use when you need a docs page and have no URL for it, or when a docs URL you tried returned 404. Not for making a change to an app's Adapty setup — connecting a store, or creating products, access levels or placements — which `adapty-integration` carries out through the Adapty CLI.
Oldhand Plan
9berwinsingh/oldhand
Plans the smallest complete code change before anything is edited: the fix point on the shared path, the files to touch and why, one regression check, scenarios for every acceptance and regression criterion (including negative, messy and the original failing case), blast radius and rollback, who does what at which model tier, and the budget for live or paid runs. Writes plan.md in the task's .oldhand folder and, in plan-only mode, stops there until the user approves. Use when the user says "how would you fix this", "what would you change" or "write the implementation plan", or after oldhand-tr
Convert State Machines to Actors
9kr4chinin/skills
Convert a database-backed implicit state machine to an actor, the one owner every writer of the persisted state goes through. Use when asked to put writers behind one owner, or to fix a race or lost update across several writers, such as a find-implicit-state-machines finding.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.