Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
The English summary is being prepared. Showing the original description.
Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.
The English summary is being prepared. Showing the original description.
Enforces Beads policy for a repository maintained initially by one owner, granting issue-management and commit authority while requiring explicit permission for Git pushes (other than to the user's own fork) and Dolt sync or push operations. Use when the user asks to enroll, repair, or operate a solo-maintainer Beads workspace, and when working with Beads in a repository that may carry a beads-solo enrollment, including when bd refuses a schema migration or mentions a remote.
The English summary is being prepared. Showing the original description.
Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
The English summary is being prepared. Showing the original description.
Generates a pull request description for the current branch and writes it as Markdown to .git/magit/posts/new-pullreq for magit-forge. Use when the user asks for a PR description, PR summary, or write-up of what a branch changes, or is preparing to open a pull request.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.
The English summary is being prepared. Showing the original description.
Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.
The English summary is being prepared. Showing the original description.
Load before the first bd command of any kind (reads included) in every session, even when bd prime context is already present. Applies reusable Beads writing and update practices when reading, creating, updating, commenting on, closing, superseding, or handing off Beads issues, alongside beads, beads-solo, and plan-to-beads workflows.
The English summary is being prepared. Showing the original description.
Review every Beads issue waiting on a person, one at a time, using the interactive questionnaire UI rather than plain-text prompts. Use when asked to go through blockers, clear the human queue, answer beads waiting on the user, triage `bd human list`, or unblock agent work that needs a decision.
The English summary is being prepared. Showing the original description.
Creates a Beads issue for a requested piece of work, completes exactly that work, and closes the issue. Use when the user invokes `/bx` or `$bx`, or asks for a bead to be created and the described work done in the same go. For creating a bead without doing the work, use the `bc` skill instead.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Open a URL or local file in the user's regular browser, including live-rendered local Markdown. Use for `/open` or when the user asks to view a target outside the agent browser.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)