Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when integrating a new requirement into an existing design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove AI-generated code slop and clean up code style
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.