Open Prompts
Submit a prompt
Coding

Constructive Review Comment Writer

Describe the issue you've spotted in plain English along with the specific lines and fuller details, and get back a ready-to-paste GitHub review comment instead of staring at a blank comment box. The output is specific, explains why the issue matters, includes a concrete suggested fix, and skips filler openers like "Great work, but..." — also useful as a template for junior reviewers learning to write good comments.

Prompt
I need to leave a code review comment on this diff. The issue I want to flag is: {{issue_summary}}. Write the review comment I should post. It should be: specific (reference the exact lines), constructive (explain why, not just what), actionable (include a suggestion or example fix), and professional but direct. Avoid filler phrases like "Great work, but..." Write it as plain text I can paste directly into GitHub.

{{code_lines}}
{{issue_details}}
Download .md

Variables

Related prompts

Coding

AI First-Pass Code Review

Paste a diff or code block and get a senior-engineer-style first pass before it reaches a human reviewer. - Flags bugs, security risks, performance issues, and maintainability problems - Rates each finding Critical, High, Medium, or Low with line references and a fix - Add project conventions (e.g. "no nested ifs") for sharper, more relevant results - Run it on every PR so reviewers only spend time on what's left after the obvious stuff is caught

Coding

Polished PR Comment Generator

Takes review notes you've already worked out — the issues, not the raw diff — and turns them into 5 polished GitHub PR comments ready to post. Each one stays direct without being harsh, names the specific issue, explains its impact, and suggests a fix, capped at 80 words so reviewers actually read it. Useful when you already know what's wrong and just want the wording tightened before publishing.

Coding

Git commit message writer

Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.