Coding agents · in Claude Code only

Claude Code for Claude Code only

Plan + write + fix in the Claude Code only stack. 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.

· 1 weeks ago
Where Claude Code fits in the workflow
  1. 1
    Open a session

    `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. 2
    Open the PR

    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. 3
    Triage CodeRabbit, in-session

    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}}
    """
Cost in this stack
Free tier
Of the $0/mo solo oss maintainer budget
Tool pricing
Bundled with Claude Pro $20/mo · Max $100-200/mo · API metered
Alternatives to Claude Code at this step
Other tools in the Claude Code only stack
Other stacks using Claude Code
See the full Claude Code only stack
Workflow, costs at three usage tiers, prompts, pitfalls.
Spotted something off?
Wrong price, dead link, stale tool — anything. We review every fix.
Suggest a fix to this tool