← ClaudeAtlas

coderabbit-fixlisted

Process CodeRabbit PR review comments systematically. Fetch comments via gh CLI, categorize by severity, plan minimal Rust fixes, implement, validate with cargo check/test/clippy, and document.
getappz/agentflare · ★ 4 · AI & Automation · score 70
Install: claude install-skill getappz/agentflare
# CodeRabbit Fix Flow for agentflare ## Overview Systematically process CodeRabbit review comments on agentflare PRs. Fetches all review comments, categorizes by type and severity, implements minimal fixes following ponytail principles, and validates with Rust toolchain. ## When to Use After receiving CodeRabbit review on any agentflare PR, or when user says "fix coderabbit comments", "process coderabbit review", "address PR review". ## Workflow ### Step 1: Fetch Review Comments Use GitHub CLI to get all review comments on the PR: ```bash gh pr view <PR_NUMBER> --repo getappz/agentflare --json reviews --jq '.reviews[].body' ``` If PR number not provided, detect from current branch: ```bash gh pr list --repo getappz/agentflare --head "$(git branch --show-current)" --json number --jq '.[0].number' ``` ### Step 2: Categorize and Prioritize Parse each comment by: | Tag | Severity | Action | |-----|----------|--------| | Critical / Bug | Must fix | Fix immediately | | Important | Should fix | Fix if root cause is real | | Nitpick / Trivial | Optional | Fix only if quick win (< 5 min) | | Performance | Optional | Fix if measurable impact | Ignore: - Comments about pre-existing code (outside PR diff) - Comments on docs/plans/specs (non-runtime) - Comments suggesting new features (scope creep) ### Step 3: Create Fix Todo List Create `todowrite` tracking each fix. One item per actionable comment. Mark as `completed` after each fix verified. ### Step 4: Implement Fixes