#code review agent

Code Review Agent Prompt: System Prompt With Severity Rules

Generate a system prompt for an AI code review agent from your repo conventions: scope, severity levels, what to ignore, comment format, and when to stay quiet.

Act as a staff software engineer and AI agent designer who writes system prompts for automated code review agents that leave few, precise, evidence backed comments on pull requests. Inputs: - Languages, frameworks, and key libraries in the repo: [RepoStack] - Team conventions the agent should enforce (naming, error handling, testing, logging, security rules): [TeamConventions] - What matters most in review, in priority order: [ReviewPriorities] - What the agent must never comment on (formatting handled by the linter, generated files, lockfiles): [IgnoreList] - Where the agent runs and what it can see (diff only or full repo, can it run tests, comment limits): [AgentSetup] - How comments should look (inline vs summary, tone, suggestion blocks): [CommentFormat] - False positives the team is tired of seeing: [KnownFalsePositives] Generate: 1. The full system prompt for the code review agent, ready to paste. It must include: the agent's role, its scope as limited by AgentSetup, ReviewPriorities in order, severity levels (blocker, major, minor, nit) with a one line definition and an example from RepoStack for each, the IgnoreList as hard rules, CommentFormat, a maximum number of comments per review, and an instruction to say the change looks good when nothing meets the bar. 2. An evidence rule inside the prompt: every comment names the file and line from the diff, states the concrete failure scenario, and suggests a fix. No comments that only say something might be a problem. 3. An uncertainty rule: when the agent cannot see enough context, it asks one question instead of making a claim. 4. A summary comment template the agent posts once per review. 5. Five test diffs described in a sentence each, with the expected agent behavior, including one clean diff where the right output is no inline comments. 6. Tuning notes: a rule for each item in KnownFalsePositives, and what to change if the agent is too noisy or too quiet. Rules: - Do not describe features of any specific review platform that are not in AgentSetup. - Keep the system prompt under 600 words so it stays readable and cheap to run.