스킬 찾기

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".

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

Analyze task complexity and route to a mode by artifact: direct fix for clear-scope changes, or a plan file when the approach needs to be written down. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".

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

Shared rules for test runs that drive the running app or run a test target: isolation from concurrent runs, stubs for infrastructure that cannot be stood up, provisioning privileged state, approval before writes to shared external systems, and cleanup of only what the run created. Not typically invoked directly.

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

Run an independent peer review via Claude. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "get a second opinion", or "independent review".

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

Update installed Turbo Codex skills from the local repo with a dynamic changelog, conflict resolution for customized skills, and guided user experience. Use when the user asks to "update turbo", "update turbo skills", "reinstall turbo", "upgrade turbo", or "update turbo for codex".

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

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".

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

Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers comments that misdescribe the code, what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "fix stale comments", "reduce doc noise", or "run simplify-docs".

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

Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change, reading any source the task names outside this repo. Returns structured findings without writing code. Use when the user asks to "survey patterns", "find existing patterns", "look for analogous features", "check how similar things are done", "find prior art for this change", or needs pattern context before planning a change.

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

Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.

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

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.

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

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".

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

Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past sessions", "extract lessons from all sessions", "save learnings", "update AGENTS.md with what we learned", "capture session insights", "remember this for next time", "extract lessons", "update skills from session", or "what did we learn".

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

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".

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

Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".

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

Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests", "run the test suite", "check that this passes", "does this pass CI", or "run the project's checks".

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

Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past sessions", "extract lessons from all sessions", "save learnings", "update CLAUDE.md with what we learned", "capture session insights", "remember this for next time", "extract lessons", "update skills from session", or "what did we learn".

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

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 and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit my changes", or "commit these changes".

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

Upgrade project dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade packages", "upgrade dependencies", "update deps", "upgrade deps", "update npm deps", "update Swift packages", "cargo update", "go get updates", "bundle update", "pip upgrade", or "update GitHub Actions".

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

Update installed Turbo skills from the local repo with a dynamic changelog, conflict resolution for customized skills, and guided user experience. Use when the user asks to "update turbo", "update turbo skills", "reinstall turbo", or "upgrade turbo".

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

Consult Claude Code for second opinions, brainstorming, or difficult debugging from Codex. Use when the user asks to "consult claude", "ask claude", "get claude's opinion", "brainstorm with claude", or "discuss with claude".

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

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".

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

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 Codex session history). 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".

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

Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".

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