一键导入
autofix
Auto-fix CodeRabbit review comments - get CodeRabbit review comments from GitHub and fix them interactively or in batch
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Auto-fix CodeRabbit review comments - get CodeRabbit review comments from GitHub and fix them interactively or in batch
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | autofix |
| description | Auto-fix CodeRabbit review comments - get CodeRabbit review comments from GitHub and fix them interactively or in batch |
| version | 0.1.0 |
| triggers | ["coderabbit.?autofix","coderabbit.?auto.?fix","autofix.?coderabbit","coderabbit.?fix","fix.?coderabbit","coderabbit.?issues?","show.?coderabbit","get.?coderabbit","cr.?autofix","cr.?fix"] |
Fetch CodeRabbit review comments for your current branch's PR and fix them interactively or in batch.
gh (GitHub CLI) - Installation guidegitVerify: gh auth status
coderabbitai, coderabbit[bot], coderabbitai[bot])AGENTS.md)Before any autofix actions, search for AGENTS.md in the current repository and load applicable instructions.
Check: git status + check for unpushed commits
If uncommitted changes:
If unpushed commits:
git push, inform "CodeRabbit will review in ~5 min", EXIT skillOtherwise: Proceed to Step 2
gh pr list --head $(git branch --show-current) --state open --json number,title
If no PR: Ask "Create PR?" → If yes: create PR (see github.md § 5), inform "Run skill again in ~5 min", EXIT
Fetch PR review threads (see github.md § 2):
gh api graphql ... pullRequest.reviewThreads ... (see github.md § 2)Filter to:
isResolved == false)coderabbitai, coderabbit[bot], coderabbitai[bot])If review in progress: Check for "Come back again in a few minutes" message → Inform "⏳ Review in progress, try again in a few minutes", EXIT
If no unresolved CodeRabbit threads: Inform "No unresolved CodeRabbit review threads found", EXIT
For each selected thread:
Extract from each comment:
_([^_]+)_ \| _([^_]+)_ → Issue type | Severity<details><summary>🤖 Prompt for AI Agents</summary> (this is the fix instruction)
Map severity:
Display in CodeRabbit's original order (already severity-ordered):
CodeRabbit Issues for PR #123: [PR Title]
| # | Severity | Issue Title | Location & Details | Type | Action |
|---|----------|-------------|-------------------|------|--------|
| 1 | 🔴 CRITICAL | Insecure authentication check | src/auth/service.py:42<br>Authorization logic inverted | 🐛 Bug 🔒 Security | Fix |
| 2 | 🟠 HIGH | Database query not awaited | src/db/repository.py:89<br>Async call missing await | 🐛 Bug | Fix |
Use AskUserQuestion:
Route based on choice:
For each "Fix" issue (CRITICAL first):
If "Apply fix":
If "Defer":
If "Modify":
For each "Fix" issue (CRITICAL first):
✅ Fixed: [Issue Title] at
[Location]Agent prompt: [prompt used]
After all fixes, display summary of fixed/skipped issues.
If any fixes were applied:
git add <all-changed-files>
git commit -m "fix: apply CodeRabbit auto-fixes"
Use one commit for all applied fixes in this run.
If a consolidated commit was created:
AGENTS.md instructions already loaded in Step 0 (if present).If a consolidated commit was created:
git pushIf all deferred (no commit): Skip this step.
If fixes were applied, post a fixes summary. If none were applied, post a neutral review-status summary:
# When fixes were applied:
gh pr comment <pr-number> --body "$(cat <<'EOF'
## Autofix Review Completed
Fixed <file-count> file(s) based on <issue-count> unresolved review comment(s).
**Files modified:**
- `path/to/file-a.ts`
- `path/to/file-b.ts`
**Commit:** `<commit-sha>`
The latest autofix changes are on the `<branch-name>` branch.
EOF
)"
# When no fixes were applied (all deferred or none required):
gh pr comment <pr-number> --body "## Autofix Review Completed
No fixes applied — all issues deferred or none required."
See github.md § 3 for details.
Optionally react to CodeRabbit's main comment with 👍.
Maintain AI proposal discovery and form preparation when adding or updating Agreements create routes. Use when adding a new proposal type, changing create form fields, or updating select-create-action / select-settings-action menus.
Scaffold an SDD ticket workspace when starting a new unit of work. Reads the developer config, classifies the task, picks the SDD level, and creates the ticket folder in hypha-context. Trigger when the developer says: 'I'm starting #X', 'let's begin <ticket>', 'new task', or 'starting work on X'. (To resume an in-progress ticket use hypha-task-resume. To wrap up use hypha-checkpoint.)
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.
Surface an idea, observation, or proposal for team discussion without owning the improvement — creates a committed entry in the shared feedback/ folder in hypha-context. Two flavors: internal (engaged dev flagging something to discuss collectively) or external (any contributor providing input for engaged devs to act on). Trigger when someone says: 'flag this for the team', 'I have feedback on X', 'log this idea without a ticket', 'note this for discussion', 'I want to surface this but not own it'.