Generate GitHub Issue and PR Templates for Your Project
Good issue templates prevent low-quality bug reports, and PR templates ensure reviewers get the context they need — let Claude write them from your project's conventions.
claude -p "Read my project structure and README, then generate GitHub issue templates for bug reports and feature requests, plus a PR description template. Match the tech stack and test commands you can see in the project."
Claude creates properly structured files in .github/ISSUE_TEMPLATE/ and a pull_request_template.md tailored to your stack — referencing your actual test commands, CI steps, and the right labels:
## Bug Report
**Describe the bug**
A clear description of what happened.
**To Reproduce**
1. Run `php artisan serve`
2. Navigate to...
**Expected vs Actual behaviour**
**Environment**
- PHP version:
- Laravel version:
- Browser (if applicable):
If you already have templates that aren't being filled in properly, ask Claude to rewrite them to guide contributors more explicitly:
cat .github/pull_request_template.md | claude -p "Rewrite this PR template to prompt contributors more clearly. Add checklist items for tests, documentation updates, and breaking changes."
Five minutes with Claude means every future contributor fills in the right information — without you having to ask.
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.