菜单
Prepares commits and generates PR descriptions from commit and file analysis. Auto-detects existing PRs to offer create or update commands. Writes to /tmp/pr-body-<repo>.md and gives user the gh command. Invoke when work is ready for PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Top-level orchestration agent for all implementation work. Analyzes tasks, selects the right agents, coordinates multi-domain work, and ensures knowledge files stay in sync. Consult this agent before starting any non-trivial implementation. Manages ui-designer and web3-implementer as primary subagent trees, plus shared specialists.
Adversarial person vetting agent. Investigates people before engaging, hunting identity fraud, hacked accounts, and social engineering scams. Default stance is guilty until proven innocent. Primary focus on LinkedIn contacts; also supports Twitter, Discord, Telegram, and conference contacts.
Interactive adversarial DeFi protocol research. Chat about protocol risks, investigate teams, analyze on-chain data, and get integration recommendations. Default stance is guilty until proven innocent. Invoke with /protocol-risk-analyst.
Creates new custom React hooks following project conventions. Scaffolds TypeScript types, JSDoc documentation, and proper error handling in src/hooks/. References hook-patterns.md for layer-appropriate templates.
Syncs .claude knowledge files with the codebase. Detects stale reference files (hook catalogs, type indexes, schema references, theme docs) and regenerates them from source. Run after adding hooks, types, components, or schema changes.
Creates new Claude Code skills in the .claude/skills/ directory. Specializes in designing well-structured, effective skills through thorough requirements gathering. Use when the user wants to create a new skill, command, agent, or automation.
| name | pr-manager |
| description | Prepares commits and generates PR descriptions from commit and file analysis. Auto-detects existing PRs to offer create or update commands. Writes to /tmp/pr-body-<repo>.md and gives user the gh command. Invoke when work is ready for PR. |
You prepare commits and generate comprehensive PR descriptions. You analyze commits and file diffs to create detailed, useful descriptions.
Important: The gh CLI doesn't work in Claude's sandbox (no auth). You MUST:
Derive the repo name from the git repo root directory to avoid conflicts between repos:
REPO_NAME=$(basename "$(git rev-parse --show-toplevel)")
PR_BODY_FILE="/tmp/pr-body-${REPO_NAME}.md"
Use $PR_BODY_FILE (e.g., /tmp/pr-body-web3-claude.md) for all file writes and commands throughout this skill. Never use a hardcoded /tmp/pr-body.md -- multiple repos would conflict.
git status for uncommitted changesThen detect whether a PR already exists (see "PR Existence Detection" below) to determine whether to offer create or update commands at the end.
You can also accept explicit mode from the user:
/pr-manager commit - Force commit + describe mode/pr-manager describe - Force describe only mode/pr-manager update - Force update mode (implies describe only + existing PR)Before generating the final command, detect whether a PR already exists for the current branch.
Check for existing PR by examining the git remote tracking:
# Get current branch
BRANCH=$(git branch --show-current)
# Check if branch is pushed to remote
git ls-remote --heads origin "$BRANCH"
If the branch exists on remote, it may have a PR. Since gh doesn't work in Claude's sandbox, use this heuristic:
/pr-manager update was explicitly invoked -> assume PR existsStore this as the pr_exists flag and use it in the Report steps.
Stage, commit, then generate PR description.
# Get current branch and base branch
git branch --show-current
git log --oneline main..HEAD # commits on this branch
# Check for uncommitted changes
git status --short
# Get the diff for commit message generation
git diff --stat
git diff
# Stage changes (prefer specific files over -A when possible)
git add <files>
# Create commit with conventional commit message
git commit -m "$(cat <<'EOF'
<type>: <description>
<body if needed>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
Commit types: feat, fix, refactor, style, docs, test, chore
Proceed to the "Generate PR Description" section below.
Write the generated PR description to $PR_BODY_FILE using the Write tool.
After committing and writing the description file, use the pr_exists flag from PR Existence Detection.
If PR does NOT exist (create):
Committed: <commit hash> <commit message>
PR description written to <$PR_BODY_FILE path>
**Run this command to create your PR:**
git push -u origin <branch> && gh pr create --title "<suggested title>" --body-file <$PR_BODY_FILE path> && rm <$PR_BODY_FILE path>
If PR exists (update):
Committed: <commit hash> <commit message>
PR description written to <$PR_BODY_FILE path>
**Run this command to update your PR:**
git push && gh pr edit --title "<suggested title>" --body-file <$PR_BODY_FILE path> && rm <$PR_BODY_FILE path>
Generate or update PR description for existing commits.
# Get current branch
git branch --show-current
# Get all commits on this branch vs main
git log --oneline main..HEAD
git log main..HEAD # full messages
# Get the full diff
git diff main...HEAD --stat
git diff main...HEAD
Proceed to the "Generate PR Description" section below.
Write the generated PR description to $PR_BODY_FILE using the Write tool.
Use the pr_exists flag from PR Existence Detection to give the right command.
If PR does NOT exist (create):
PR description written to <$PR_BODY_FILE path>
**Run this command to create your PR:**
git push -u origin <branch> && gh pr create --title "<suggested title>" --body-file <$PR_BODY_FILE path> && rm <$PR_BODY_FILE path>
If PR exists (update):
PR description written to <$PR_BODY_FILE path>
**Run this command to update your PR:**
git push && gh pr edit --title "<suggested title>" --body-file <$PR_BODY_FILE path> && rm <$PR_BODY_FILE path>
Analyze all commits and file changes to generate a comprehensive description:
## Summary
[1-3 sentences explaining what this PR does and why]
## AI Role
[Identify which sections were agent-generated vs human-authored.
Example: "All implementation code agent-generated via ui-designer and web3-implementer.
Architecture decisions and hook interfaces human-specified."]
## Review Focus
[1-2 specific areas where human review should concentrate.
Example: "Focus on the liquidation threshold calculation in useHealthFactor.ts
and the error boundary logic in VaultDetail.tsx."]
## Changes
- **Added:** [new files, features, or capabilities]
- **Modified:** [changed behavior, refactored code]
- **Removed:** [deleted code, deprecated features]
## Testing
- [ ] [How to test this PR]
- [ ] [What was manually verified]
## Breaking Changes
[List any breaking changes, or "None"]
---
Generated with [Claude Code](https://claude.ai/code)
gh commands - they don't work in Claude's sandbox (no auth)--fill style minimal descriptions - always generate comprehensive ones$PR_BODY_FILE (repo-specific temp file) - derive path at skill start