Oldhand Build
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
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-buildgit clone --depth 1 https://github.com/berwinsingh/oldhand.git /tmp/oldhand
mkdir -p ~/.claude/skills
cp -r /tmp/oldhand/skills/oldhand-build ~/.claude/skills/oldhand-buildPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# oldhand-build
The build turns `plan.md` into the smallest diff that meets every criterion, and leaves proof: a
regression check that fails without the fix, and repo checks no worse than before the first edit.
## What the user typed
`$ARGUMENTS`: the text after the skill name (other hosts: the message that started this skill). Blank:
build the whole plan. A slice name or a file list limits the build to that part.
## Reads and writes
`LEDGER` below means `python3 "${CLAUDE_SKILL_DIR}/../oldhand/scripts/ledger.py"` and `MUTATE` means
`python3 "${CLAUDE_SKILL_DIR}/scripts/mutate.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. `D` is the task folder.
Reads `D/contract.md`, `plan.md`, `trace.md`, `rca.md`, `research.md`. Writes the source and test
files `plan.md` names, `D/build.md`, command output in `D/build/`, and ledger records of kind unit,
integration and mutation.
## Step 1: Load the task and check the mode
`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`, `contract.md` with 2-6 `- AC1: ... (proof: e2e)` lines listed as derivedDetails
- Skill name
oldhand-build- Repository
- berwinsingh/oldhand
- Path
skills/oldhand-build/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Oldhand Build skill do?
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
How do I install the Oldhand Build 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 Build 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 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
Oldhand Learn
9berwinsingh/oldhand
Captures the durable, non-obvious lessons from a task (diagnosis recipes, API and platform quirks, environment traps, failed experiments with their numbers, decisions and their why, rollback points, user corrections) into the project's existing agent instruction file or the host's memory system, each note dated with why and how to apply, and corrects or deletes notes the task proved wrong. Use when the user says "write down what we learned on this task", "save the lessons from this task", "capture this task's lessons for next time", or at the end of the oldhand chain. Not for documenting code
Cj Dropshipping API
9simoncai519/open-accio-skill
Use when user wants to integrate CJ Dropshipping, search products, create orders, track shipments, manage Shopify listings via CJ, or automate CJ logistics and webhook setups. Triggered for CJ API related tasks like product queries, order creation, shipping calculations, delivery profile management, and webhook configuration.
Procedural Grounded Theory
5maydengximin-sketch/procedural-grounded-theory-skill
程序化扎根理论(Procedural / Straussian Grounded Theory, Strauss & Corbin)专项方法学助手,聚焦"用一套系统化的编码程序与工具,从质性资料中建构出一个结构清晰的解释性理论"的完整链路——不是泛扎根,也不是经典 Glaser / 建构主义 Charmaz,而是专攻 Strauss & Corbin / Corbin & Strauss 一脉的程序化取向。当用户要做程序化扎根理论的任何环节时使用:判断"我该用程序化扎根,还是经典 Glaser / 建构主义 Charmaz / 主题分析 / 现象学"、写清程序化扎根的认识论立场(后实证到实用主义、符号互动论根基、Strauss 与 Glaser 因"涌现 vs 强加 emergence vs forcing"分道、1990/1998/2008/2015 版本演变)、研究问题与理论敏感性(theoretical sensitivity)与文献的位置(程序化允许文献作为敏感性来源)、开放编码(概念化、贴标签→概念→范畴、属性与维度 properties & dimensions、逐行微观分析、提问与比较)、主轴编码(编码范式 coding paradigm:因果条件—现象—脉络—中介条件—行动/互动策略—结果,把范畴与子范畴按范式重连而非归类)、选择性编码(核心范畴判定标准、故事线 s
Solid Design Patterns
9lvcoi/solidJSkills
Choose SolidJS architecture patterns with explicit tradeoffs, migration paths, and deterministic recommendation rules. Use when deciding state ownership, rendering/data flow, or boundary design.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.