# Claude Code only > If you live in the terminal, you don't need a chat tab next to your editor. Claude Code can plan a change, edit the files, run the tests, and stage the commit — all in one session. CodeRabbit reviews the PR; you bounce findings back to the same Claude Code session for fixes. Source: https://aistack.sh/stack/ship-code-claude-code Category: Code · Workflow Level: Intermediate Last verified by a human: 2026-05-05 ## The tools ### Claude Code — Plan + write + fix - Pricing: Bundled with Claude Pro $20/mo · Max $100-200/mo · API metered - Site: https://claude.com/code - Why this one: Give it the ticket, it produces a plan, asks clarifying questions, then implements. Skills encode your repo conventions; hooks gate dangerous commands. Subagents handle reviews and verifications without polluting the main thread. - Swap in instead: Codex, Cursor - More: https://aistack.sh/tool/claude-code ### CodeRabbit — Automated PR review - Pricing: Free for OSS · $30/mo per dev Essentials ($24 billed annually) · $60/mo Team · $90/mo Advanced - Site: https://coderabbit.link/aistacksh - Why this one: Same role as the recommended stack. The CLI-only loop pairs especially well with CodeRabbit because the agent can pipe `gh pr view` straight into its own context to fix findings without you copying anything. - Swap in instead: Claude - More: https://aistack.sh/tool/coderabbit ## Monthly cost ### $0/mo — Solo OSS maintainer (small) - Claude Code: Free tier - CodeRabbit: Free (OSS) ### $50/mo — Indie dev, daily PRs (medium) - Claude Code: $20 Pro - CodeRabbit: $30/dev ### $250/mo — Heavy agentic use, multiple parallel sessions (heavy) - Claude Code: $100 Max - CodeRabbit: $150 (5 devs) ## Workflow ### 1. Open a session (Claude Code) `cd repo && claude`. Hand it the ticket as the first message. Let it ask the clarifying questions a chat tab would have surfaced. **Prompt: Plan-and-implement from a ticket (Claude Code)** ``` I want a small, well-scoped PR for the change below. Plan first, then implement. Ask 1 to 2 clarifying questions before you start writing if anything is genuinely ambiguous. Ticket / problem: """ {{paste ticket}} """ Constraints: - Smallest viable diff. - Match the existing code style. Read 2 to 3 nearby files before introducing a new pattern. - Run the project's test command before reporting done. - If a CLAUDE.md or AGENTS.md exists at the repo root, treat it as authoritative for conventions. When you're done: print the file list, the test result, and a 2-line summary I can paste as the commit message. ``` ### 2. Open the PR (Claude Code) Use Claude Code's `/pr` workflow (or `gh pr create`). It writes the PR description from the diff. CodeRabbit posts its review within ~60s. ### 3. Triage CodeRabbit, in-session (Claude Code) Pipe the review into the same Claude Code session: `gh pr view --json comments | claude`. The agent sees the findings, the diff, and the codebase together — no copy-paste. **Prompt: Triage and patch CodeRabbit findings inside Claude Code** ``` I just opened a PR. CodeRabbit posted comments. I'm pasting them below. For each comment: 1. Decide: real issue, style nit, or wrong (false positive). 2. For real issues + non-trivial nits: produce a minimal patch. Run the tests. Reply on the PR explaining the fix. 3. For false positives: write a 1-line PR reply explaining why we're declining, no code change. Do NOT batch-resolve nits without reading them. Do NOT introduce changes outside the scope of each comment. CodeRabbit comments: """ {{paste 'gh pr view --json comments' or the comment thread}} """ ``` ### 4. Re-review and merge (CodeRabbit) Push fixes; CodeRabbit re-reviews. Merge once it's quiet and the human review is approved. ## What it produced **Solo founder, comparison week** Ran the same 8 tickets through this stack and the chat-led recommended stack. Time-to-merge dropped from 90 to 55 min/PR average. The trade-off: 2 of the 8 tickets needed a chat-tab debate before the agent could plan well — for those, the chat-led stack still won. ## Pitfalls - **No external rubber duck** — When you genuinely don't know what to build, a CLI agent that's already implementing is the wrong tool. Drop back to a chat tab for the open-ended part, then come back to Claude Code to ship. - **Yolo mode on a real repo** — Claude Code can run shell commands. Configure permissions and hooks before you hand it a repo with deploy credentials, migrations, or a production .env in scope. ## Verifiable artifacts - [aistack.sh — this site](https://aistack.sh) — Built mostly inside Claude Code, terminal end-to-end. 28+ passes, 40+ PRs, the full SDLC inside one CLI session per ticket. - [Source repo](https://github.com/theomarsoliman/aistacksh) — AGENTS.md at the repo root encodes the conventions Claude Code reads on each session. Open it to see what 'authoritative repo conventions' looks like in practice. - [PR #29 · launch prep (sitemap + robots + 404 + error boundary)](https://github.com/theomarsoliman/aistacksh/pull/29) — Four loosely-related concerns shipped in one focused PR. Demonstrates the 'plan-and-implement in one CLI session' loop without a separate chat tab. - [PR #39 · slim /pricing under 2 MB Googlebot limit](https://github.com/theomarsoliman/aistacksh/pull/39) — Constrained, debug-flavored work — the kind of ticket that reads like 'figure out why X is too big and fix it'. Claude Code triaging and patching in the same session. ## Recent changes affecting this stack - **Unified connection management with scopes across CodeRabbit products** (2026-09-10, feature) — Configure external service connectors once, then use scopes to control access across Review, Slack, and Discord. Base and named scopes let security-sensitive repositories or channels be excluded from shared connections, reducing duplicate setup across products. Source: https://docs.coderabbit.ai/changelog - **Custom Jira issue template configuration for CodeRabbit** (2026-09-10, feature) — Teams can now configure chat.integrations.jira.issue_template to define custom Jira issue structures, ensuring CodeRabbit-created issues follow team standards instead of using default formatting. Source: https://docs.coderabbit.ai/changelog - **CodeRabbit unified external service configuration with scopes for access control across products** (2026-09-10, feature) — Service configuration is now centralized with a single setup per connector, with scopes controlling usage across repositories and chat platforms. Base scopes define defaults while named scopes can override or exclude access for specific repositories or teams, allowing security-sensitive areas to restrict connector access. Source: https://docs.coderabbit.ai/changelog - **CodeRabbit supports custom Jira issue templates for team-specific standards** (2026-09-10, feature) — Developers can configure custom Jira issue description structures through the chat.integrations.jira.issue_template setting instead of using CodeRabbit defaults. This ensures created issues match team formatting and field requirements. Source: https://docs.coderabbit.ai/changelog - **CodeRabbit unifies connector configuration with connections and scopes** (2026-09-10, feature) — Developers can now configure connectors once instead of separately for pull request reviews, Slack, and Discord. Named scopes control which products can use each connector in specific repositories or channels, eliminating duplicate setup and improving security control for sensitive repositories. Source: https://docs.coderabbit.ai/changelog ## Other ways to do this - [Ship code with AI](https://aistack.sh/stack/ship-code-with-ai): Plan in Claude chat, write in Claude Code, review with CodeRabbit — $50/mo - [Antigravity (Google)](https://aistack.sh/stack/ship-code-antigravity): Google's AI IDE: Gemini 2M-context inside the editor — $40/mo - [Codex (CLI + cloud)](https://aistack.sh/stack/ship-code-codex): OpenAI Codex: terminal CLI for active work, cloud lane for autonomous PRs — $40/mo - [Cursor (IDE-first)](https://aistack.sh/stack/ship-code-cursor): AI inside the editor, not in a chat tab or terminal — $20/mo - [Windsurf (Devin Local)](https://aistack.sh/stack/ship-code-windsurf): Cognition's IDE with the Devin Local autonomous-edit agent — $15/mo --- Curated by alex-w on aistack.sh. Last updated 2026-05-05.