スキルを探す

Run the code and documentation simplification passes together over one scope, launching every review 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".

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Update an existing GitHub pull request's title and description to reflect the current state of the branch. Use when the user asks to "update the PR", "update PR description", "update PR title", "refresh PR description", or "sync PR with changes".

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does this mean", "what does this error mean", "what is this code doing", or "what do these options mean".

日本語の概要は準備中です。原文の説明を表示しています。

Shared writing style rules for GitHub-facing output (PR comments, PR descriptions, PR titles, issues, design proposals). Differentiates insider vs outsider voice based on author association. Not typically invoked directly — loaded by other skills before composing GitHub text.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Enforce existence, reuse, mirror, and symmetry principles to keep new code minimal and consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".

日本語の概要は準備中です。原文の説明を表示しています。

Write a handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md capturing current session state — task, status, open decisions, in-flight changes, next step — so a fresh session can continue without re-deriving context. Use when the user asks to "create a handoff", "create handoff", "save handoff", "handoff before compact", "save session state", "handoff for next session", or "capture session state".

日本語の概要は準備中です。原文の説明を表示しています。

Create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when the user asks to "create a skill", "make a new skill", "build a skill", "scaffold a skill", "write a skill for...", or "new skill that does...".

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a codebase and produce a structured threat model at .turbo/threat-model.md covering assets, trust boundaries, attack surfaces with existing mitigations, attacker stories, and calibrated severity. Use when the user asks to "create a threat model", "threat model", "threat model this codebase", "security analysis", "analyze the attack surface", "what are the threats", or "identify security risks".

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message. Use when the user asks to "reply to PR conversation", "post PR conversation replies", or "draft PR conversation messages".

日本語の概要は準備中です。原文の説明を表示しています。