Skip to main content
CodeAnt AI automatically reviews every pull request you open. It analyzes your changes for security issues, bugs, code quality problems, and architectural concerns — then posts actionable feedback directly on the PR. No configuration needed — just open a PR and start receiving reviews.

​
How do I re-trigger a review?

Comment on the PR: 
@codeant-ai: review
CodeAnt AI will re-analyze the latest changes and post updated review comments.

​
How do I ask questions to CodeAnt AI?

Tag CodeAnt AI in any PR comment to ask a question about the changes: 
@codeant-ai ask: Your question here
  • Ask about the overall PR to understand the scope of changes
  • Reply to a specific line of code or review comment to get targeted, contextual answers
  • Ask follow-up questions to dig deeper into any part of the review
Learn more: Chat

​
How do I reduce false positives?

Reply to the review comment explaining why it’s not an issue: 
@codeant-ai: This is not an issue because [your reasoning]
CodeAnt AI will create a learning from your feedback and avoid similar flags in future reviews. You can manage all your learnings from CodeAnt AI Settings. Learn more: Chat

​
How do I fix a suggestion?

Each review comment includes a suggested fix with ready-to-use code.
  • If you’re confident the fix is correct — click Apply Suggestion directly on the review comment to commit the change.
  • If you want to use your AI agent — click Copy Prompt for AI on the suggestion. This copies a ready-made prompt with the full context of the issue, the fix, and the steps of reproduction. Paste it into your AI coding agent (Cursor, Copilot, Claude Code) and let it apply the fix.
Learn more: Code Review

​
How do I validate a finding?

Every review comment includes steps of reproduction — a numbered list showing the exact execution path that triggers the issue, with file paths and line numbers.
  • Read the steps yourself to trace the code flow and understand if the issue is real
  • Copy the steps into your AI coding agent and ask it to verify whether this is a valid issue in your codebase
  • Follow the steps in your local environment to reproduce the bug before fixing it
Learn more: Code Review