babysit-pr
Use after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings, replies with a…
Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is
$ npx -y skills add greenfield-inc/Pane --skill cold-read --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cold-readContext preview
The summary Claude sees to decide when to auto-load this skill.
Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is
name: cold-read description: Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is finished, or any user-facing artifact. Always dispatch as a fresh sub-agent with no conversation history - the zero context is the point.
You know nothing about this. You're seeing it for the first time at 8am with groggy eyes. Walk through it start to finish.
Report what's broken, confusing, or contradictory. Report what could be described more simply. Report what information you don't have that you need - do you know the what, why, how, when, where? Be thorough about what you don't know and what you'd need to know.
Don't fix anything. You don't have the context to know what the fixes should be. Just explain what you experienced as someone walking through this for the first time.
Use after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings, replies with a…
Use when a problem, idea, or change of intent is worth capturing as a long-form page, or the person asks to write it up. Never…
Use when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening…
Explore the codebase to locate files, trace behavior, and document existing patterns with precise file references. Use when the…
Capture work and evolving intent during discussion as one or more GitHub tickets, Grain briefs, or both. Use for ticket or issue…