understudy
/understudy
Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. Use when writing into a codebase or document you don't own: a pull request or patch to an upstream project, a fix matching a specific maintainer's style, a change that has to blend into a teammate's module. Triggers when the user invokes the understudy skill, says "match the style", "make it look like theirs", "fit the house style", "will this look out of place in their repo", or before opening a PR against someone els
- Author
- pandysp ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 20.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. Use when writing into a codebase or document you don't own: a pull request or patch to an upstream project, a fix matching a specific maintainer's style, a change that has to blend into a teammate's module. Triggers when the user invokes the understudy skill, says "match the style", "make it look like theirs", "fit the house style", "will this look out of place in their repo", or before opening a PR against someone els
Triggers from the description
Original author description
Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. Use when writing into a codebase or document you don't own: a pull request or patch to an upstream project, a fix matching a specific maintainer's style, a change that has to blend into a teammate's module. Triggers when the user invokes the understudy skill, says "match the style", "make it look like theirs", "fit the house style", "will this look out of place in their repo", or before opening a PR against someone els
How it works
- The method
- Style, not substance
- Common pitfalls
SKILL.md preview
--- name: understudy description: >- Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. Use when writing into a codebase or document you don't own: a pull request or patch to an upstream project, a fix matching a specific maintainer's style, a change that has to blend into a teammate's module. Triggers when the user invokes the understudy skill, says "match the style", "make it look like theirs", "fit the house style", "will this look out of place in their repo", or before opening a PR against someone else's project. Also invoke proactively whenever you're about to write into code or prose whose style isn't your own. A foreign-looking contribution is a cost to the maintainer even when it's correct, and the cheapest time to match their hand is before you've written in yours. --- # Understudy: write as the maintainer A maintainer rejects foreign-looking code even when it's correct. A patch in the wrong idiom is a cost to them (something to mentally translate, reformat, or turn down), so a contribution that doesn't look like theirs raises the bar to merging it, sometimes past the point they'll bother. Your default makes this worse: a generic, competent style that quietly announces "written by an outsider", the same tell that reads as AI. This skill is the discipline of effacing your own hand and writing as the host, so the work arrives already in their voice and costs nothing to accept. The bar you're aiming for: **a reviewer can't find the seam between your code and theirs.** ## The method ### 1. Sample how they actually write Read the host's own code, comments, tests, and commit messages. Read more than the one thing you're touching. The hand shows in naming, comment density and what they bother to comment at all, where state lives, how errors flow, how config is gated, how tests are shaped, how commits are phrased. You'll default to glancing at the code and writing; the work is reading enough that their conventions, not your habits, are what's loaded when you start. ### 2. Iterate past your first pass One reading anchors on your own habits with a thin coat of theirs, and the idioms you'd get wrong are the ones it doesn't reveal. Keep sampling until a pass comes up dry. You should be able to name what each pass turned up, not just say you "matched the style". The pull to call it done early is the failure this skill exists to counter; when in doubt, sample again. ## Style, not substance Effacing your hand is about how the code reads, not about silencing your judgment. Match their style; don't defer on substance. If something looks wrong on the merits (a bug, a risk, a real design problem), raise it as you would anywhere. The skill doesn't tell you whether to match or push back on that; it only asks that your style be theirs, not that your opinions go quiet. ## Common pitfalls - **Declaring convergence after one pass.** The first draft is your priors lightly painted over. If you found nothing to fix on the second pass, you didn't sample hard enough. - **Cosmetic matching.** Getting the formatting right while the structure (allocation, state placement, helper reuse) stays in your own dialect. The code reads as theirs at a glance and as an outsider on a real read. - **Correct but foreign.** A technically perfect patch in your style. To a minimalist maintainer that's still a rejection; correctness is necessary, nativeness is what gets it merged.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · pandysp/claude-plugins | 90 | MIT |
| understudylabs/understudy-agent-tools | 100 | MIT |
Database snapshot: 13.11.2026 · package version 12f75b66665d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100chameleon
Match the house style when adding code to an existing codebase. Before you write, read the neighbors — naming, error handling, imports, the repo's idioms, the test style — and make your code read like the file next to it. Reuse the project's own helper, wrapper, or Result-type… - 100use-understudy-gateway
Use when a developer wants to run inference or evals through the Understudy gateway — "route my app through Understudy", "set up my account and keys", "A/B a model on part of my traffic" — or must choose between local provider keys and the gateway route ("should I use my OpenAI… - 95humanize-writing
Rewrites text to remove AI-generated writing patterns (34 tell categories spanning content, language, style, and communication) while preserving meaning, coverage, and the author's voice. Use when writing or editing a design document, README, code comment or docstring, user… - 100install-plugin
Compatibility shim for Claude Code installs. Use when a developer asks to install, update, enable, reinstall, remove, or verify the Understudy Claude Code plugin - "install Understudy in Claude", "add the Understudy skills", "why can't Claude see the skill". Route to… - 100house-style
Writes the commit, branch, and pull request for a contribution the way that repository's maintainers expect, learned from its contributing guide, PR template, CI, and recently merged pull requests. Use before committing to or opening a PR against a project the user doesn't… - 100oss-contributor
Contribute to someone else's open-source repo the way a maintainer would want. Read the house rules first, screen the claim before touching code, mirror the repo's own accepted patterns, test honestly, and open a clean PR. Use when the user wants to contribute to an external…