Tobias Hagemann

Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Use when the user asks to "triage improvements", "triage the backlog", "clean up the backlog", "clean up improvements", "groom the backlog", "prune the improvements backlog", or "go through the backlog with me".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than $smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", "find bugs by testing", "test usability", or "check the UX while testing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute an implementation plan file produced by $draft-plan or $turboplan. Runs pre-implementation prep, then runs $implement to execute the steps and finalize once they are all done. Use when the user asks to "implement plan", "implement the plan", "execute the plan", "run the plan", "implement plans/<slug>.md", "start implementing the plan", or starts a fresh session to implement a previously drafted plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not a unit test runner.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recall why a past change was made, drawing on Codex session history when available and falling back to commit diff and surrounding code. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the code and documentation simplification passes together over one scope, launching every review sub-agent concurrently before applying a single round of fixes. Use when the user asks to "simplify all", "simplify everything", "simplify code and docs", "clean up code and docs", "run both simplify skills", or "simplify code and docs in parallel".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Use after $evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to "claude print", "ask claude", "run claude", "consult claude", or when a Codex Turbo skill needs Claude as an independent peer reviewer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stand up the project's live app and hand it to the user to try a change firsthand, then act on their verdict once they reply. Use when the user asks to "preview the change", "let me try it", "spin up the app so I can test it", "set it up so I can poke at it", or before finalizing a UI/UX change that needs human eyes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a self-contained local prototype at .turbo/prototypes/<slug>.html, drive it, and hand it to the user to settle unknowns that prose cannot answer. Use when the user asks to "prototype this", "build a prototype", "mock this up", "show me what it would look like", "let me try the interaction first", or when a decision waits on seeing a surface or using it firsthand.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the full review", or "ship this without the deep pass".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Iteratively review and revise a plan until no new findings survive evaluation. Use when the user asks to "refine the plan", "iterate on the plan", "tighten the plan", or "improve the plan".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Use after /evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using the rationale recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit the turbo skill lessons that /self-improve writes into this repo's .turbo/handoff/ from other projects, apply the ones the user approves, delete the consumed handoffs, commit and push, and update the installed Turbo skills. Use when the user asks to "read .turbo/handoff and let me know what you think", "read the handoff files and let me know what you think", "review the lesson handoffs", "apply the self-improve handoffs", or "process the turbo handoffs".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect package managers and CI action pins, then discover outdated or vulnerable dependencies. Returns structured findings without upgrading. Use when the user asks to "review dependencies", "check for outdated packages", "check dependencies", "scan dependencies", "dependency review", "check for outdated GitHub Actions", or "are my workflow actions up to date".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely stuck", "I've tried everything", or "nothing is working".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze what changed and generate a structured test plan at .turbo/test-plans/<slug>.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios", "test plan for this PR", or "what are the test cases".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.