Give Claude a GitHub Issue and Let It Read, Understand, and Implement the Fix
GitHub issues are natural specifications — they describe what's broken, what's expected, and often include reproduction steps. Instead of reading an issue and translating it into prompts, just hand it to Claude.
> fix https://github.com/acme/app/issues/247
Claude uses the gh CLI to read the issue — title, body, labels, comments, and any linked PRs — then explores your codebase to find the relevant files, understands the problem in context, and implements the fix.
This works because issues contain exactly the information Claude needs: what the user expected, what actually happened, and often the steps to reproduce. Claude maps that to your code and figures out what needs to change.
You can also reference issues by number if you're already in the repo:
# If gh is configured for the current repo
> read issue #247 and fix it
# Or be more specific about what you want
> read issue #183 and just write the test — don't fix the code yet
For more complex issues, combine it with plan mode:
> /plan read issue #392 and propose a fix — it's a performance issue
> with the dashboard loading slowly for users with many projects
Claude reads the issue, explores the relevant code paths, and presents a plan before making changes — so you can review the approach before it starts editing.
After implementing, you can even have Claude create the PR:
> now create a PR that fixes #247 — reference the issue in the description
Claude stages the changes, writes a PR description that references the issue, and creates it via gh pr create — closing the loop from issue to implementation to PR.
An issue is already a spec — paste the link, and Claude goes from bug report to working fix without you restating the problem.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.