メニュー
Solve a GitHub issue end-to-end: fetch issue, create branch in worktree, launch team-develop agents. Use when: 'solve issue', 'fix issue', 'implement issue', 'work on #N'.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate a continuous improvement cycle: spawn rust-live-tester for live testing, rust-researcher for dependency monitoring and research, rust-arch-analyst for code quality and architecture review, and rust-security-analyst for vulnerability scanning. Aggregates findings and produces a cycle summary.
Initialize a Rust project for the rust-agents plugin: scaffold .local/ working directories, .claude/rules/ project rules, testing knowledge base, and .gitignore. Run once when starting a new project.
Vulnerability and security-hardening audit protocol for Rust projects. Activates expert knowledge across dependency advisories, unsafe code, secret exposure, injection and input validation, cryptography misuse, authentication and authorization, panic-based denial of service, and supply-chain trust. Called by rust-security-analyst at startup via Skill(...). When invoked directly as /security-audit [focus], the current session runs the audit without spawning subagents.
Reference for stable Rust APIs added in versions 1.89 through 1.97 (August 2025 - July 2026). Use this skill whenever writing, reviewing, or refactoring Rust code — especially when you notice patterns that were verbose before newer APIs existed, when MSRV allows it, or when the user mentions modernizing Rust code, upgrading MSRV, or using "the latest Rust features". Also trigger when reviewing Rust code for improvements, migrations, or when a user asks "can this be simpler in modern Rust?" Proactively suggest newer APIs when you see patterns like manual UTF-8 truncation, path extension manipulation, advisory file locking via external crates, ignoring `retain` removal results, verbose `try_into().unwrap()` for fixed arrays, `compare_exchange` loops for atomic update, `cfg_if` crate usage, matching `0`/`1` to `bool`, `assert!(matches!(...))` in tests, or hand-rolled bit-manipulation idioms like `1 << (BITS - 1 - x.leading_zeros())`.
Debug Rust issues using a multi-agent investigation team. Workflow: debugger + live-tester (conditional) investigate root cause in parallel → security review always, architect and perf reviews conditionally → code reviewer consolidates findings → results presented to user. Requires rust-agents plugin and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Orchestrate Rust development using agent teams with peer-to-peer communication. Use when: 'create rust team', 'start team development', 'launch agent team', 'team workflow', 'collaborative development'. Requires rust-agents plugin and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
| name | solve-issue |
| description | Solve a GitHub issue end-to-end: fetch issue, create branch in worktree, launch team-develop agents. Use when: 'solve issue', 'fix issue', 'implement issue', 'work on #N'. |
| argument-hint | <issue-number> |
Solve a GitHub issue end-to-end using the team-develop agent workflow.
Issue: $ARGUMENTS
1. Fetch issue data and assign
Run: gh issue view $ARGUMENTS --json number,title,body,labels,milestone
Then assign the issue to yourself:
Run: gh issue edit $ARGUMENTS --add-assignee @me
Parse:
number → issue numbertitle → used to derive branch slug (lowercase, spaces→hyphens, strip special chars)labels → detect bug/fix label to choose branch prefix (fix/ vs feat/)milestone → extract milestone number N for feat/mN/ branch names (if present)2. Determine branch name
Branch naming convention:
fix/<short-slug> (max 30 chars)feat/m{N}/<feature-slug> where N comes from the milestone numberfeat/issue-{number}/<feature-slug>Slug derivation: take the issue title, lowercase it, replace non-alphanumeric runs with -, trim leading/trailing dashes, truncate to 30 chars.
Note: If the project has a .claude/rules/branching.md file, read it and follow those conventions instead of the defaults above. If .claude/rules/commits-and-issues.md exists, read it for commit message format and issue filing rules.
3. Sync main branch
Run: git fetch origin main
4. Create worktree
Use the EnterWorktree tool with:
branch: the branch name derived abovebase: origin/mainThis triggers the WorktreeCreate hook and switches the session cwd automatically. Never use git worktree add directly.
5. Run team-develop workflow
Invoke the team-develop skill to orchestrate development directly (you are the team lead):
Skill(skill: "rust-agents:team-develop", args: "Implement GitHub issue #{number}: {title}\n\nIssue body:\n{body}\n\nWorking branch: {branch-name}\n\nFollow project rules in `.claude/CLAUDE.md` and `.claude/rules/` if they exist.")
EnterWorktree (never git worktree add) — the hook switches session cwd.claude/rules/, follow them