スキルを探す

Capture durable project or workflow knowledge discovered during work. Use when a mistake, hidden constraint, repeated question, or changed behavior reveals a documentation gap. To root-cause one specific mistake the agent just made and let the user pick fixes, use `learn` (`/learn`) instead.

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

Generates a minimal .editorconfig with sensible defaults for a repository. Use when starting work in a new repository, when a project has no .editorconfig, or when the user asks to add or standardise editor and formatting settings.

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

Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.

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

Review staged changes and create atomic Git commits whose messages match repository conventions. Use when the user asks to commit, write a commit message, or finalize already staged work.

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

Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.

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

Stage whole files, selected hunks, or selected lines in Git without interactive prompts. Use when preparing an exact commit boundary while preserving unrelated working-tree changes.

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

Upload images and files to GitHub PRs, issues, and comments so GitHub hosts them instead of committing binaries to the repository. Use when adding screenshots to a PR or issue body, replacing committed screenshots or raw.githubusercontent.com links with hosted attachments, or when `gh` appears to offer no way to attach a file.

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

Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.

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

Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.

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

Root-causes one specific mistake the agent just made, such as not committing despite instructions to, by checking it against the loaded AGENTS.md, CLAUDE.md, skills, and Beads memories, delegating the investigation to a separate agent where the harness supports one; proposes concrete context improvements, and lets the user choose which to apply and how to remediate. Use when the user invokes `/learn` or `$learn`, with or without a description of the mistake, including `/learn /qs`-style shorthand naming the corrective command. For a broad end-of-session documentation sweep, use `documentation-updates` (`/reflect`) instead.

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

Manages Pi packages across their lifecycle: discovers, audits, installs, upgrades, removes, enables, disables, filters, and configures extensions, skills, prompts, and themes from npm, Git, or local sources. Use before any Pi package install or upgrade, when reviewing available updates, changing package activation or configuration, or maintaining the package inventory.

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

Applies local lessons to every use of the Orca CLI (orca-ide, orca-dev). Use alongside the upstream orca-cli skill whenever the Orca CLI is needed, including before creating a branch worktree or asking the user for feedback on a change before committing while running inside Orca.

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

Triages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.

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

Puts the agent into a cautious production mode for live systems: read-only inspection may proceed, but credentials and out-of-scope personal data need permission first, every state-changing action needs explicit per-action approval with its resource risks and rollback stated, and anything unexpected halts work until the user decides. Use when the user invokes `/prod` or `$prod`, or says they are working on production, a live or customer-facing server, a mail server, or a production database, or asks for care on a system where mistakes affect real users.

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

Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.

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

Re-asks the most recent question through the agent's interactive questionnaire tool instead of plain text, and keeps using that tool for every later question with concrete options. Use when the user invokes `/qs` or `$qs`, or asks for a question to be re-posed as selectable choices.

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

Deletes files and directories through a wrapper that avoids the usual per- command permission prompt. Use only when content must genuinely be deleted, such as clearing build artifacts or dropping obsolete files during a refactor. Moves, renames, and relocations that preserve content use mv instead.

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

Gives a repository one idempotent, repo-local worktree setup script (local env files, dependency install, build steps) that worktrunk's `.config/wt.toml` pre-start hook and Orca's `orca.yaml` scripts.setup both call, so every new git worktree is usable at once. Use when adding or fixing worktree setup hooks, writing `wt.toml` or `orca.yaml` setup, when new worktrees lack dependencies or `.env` files, or when asked to make worktrees "just work" in a repo. For creating a worktree in a repo that already has setup, use `git-branch-management` instead.

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

Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.

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

Preserve output from expensive one-shot commands for monitoring and later analysis. Use when rerunning a build, API query, CI inspection, or diagnostic would be costly and a managed background process is not the better interface.

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

Summarises the current session's status so a human can see where things stand and what happens next. Use when the user invokes `/sq`, asks for the status quo, session status, a catch-up, recap, or reminder where things got to, regardless of how much previous output there was.

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

Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).

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

Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.

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

Decompose an approved implementation plan into self-contained beads issues with zero guesswork. Use when breaking down a plan file into actionable beads tasks.

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