Skip to main content
Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues. You can either tag @cubic-dev-ai directly, or reply to cubic’s existing comments. Tagging cubic in a PR comment

​
Why use interactive comments

  • Ask follow-up questions about code changes without leaving the PR
  • Re-trigger AI reviews after addressing feedback
  • Get instant clarification on AI suggestions
  • Build context through natural, threaded conversations

​
How to interact with cubic

cubic responds when you:

​
1. Tag it directly

Mention @cubic-dev-ai anywhere in your comment
cubic won’t appear in GitHub’s @ mention autocomplete dropdown. GitHub doesn’t allow GitHub Apps to be included in the autocomplete list. Just type the mention manually and it will work.

​
2. Reply to its comments

Simply reply to any of cubic’s existing comments - no @ mention needed. cubic will react with 👀 to acknowledge your comment in both cases.

​
What you can do

​
Ask questions

Get instant answers about code, design decisions, or implementation details:
  • “@cubic-dev-ai will this color code work well in dark mode?”
  • “@cubic-dev-ai can you explain how this function works?”
  • “@cubic-dev-ai is there a better way to handle this error?”

​
Trigger reviews

Tag cubic to trigger a new AI review:
  • “@cubic-dev-ai”
  • “@cubic-dev-ai review this PR”
  • Or simply tag cubic with any request - it will understand you want a review
To stop an in-progress AI review, use the Cancel AI review button in the GitHub Checks UI.

​
Request fixes

Ask cubic to generate fixes for identified issues with the “Fix with cubic” button in the GitHub comment, or by tagging cubic in a comment. E.g.
  • “@cubic-dev-ai fix this issue in this branch”
  • “@cubic-dev-ai can you generate a fix for this in a new PR?”
By default, cubic either pushes commits to your PR branch or opens a fix PR targeting your feature branch based on change size. To override, say “open a fix PR” or “push commits to this PR.” Learn more about AI-powered code fixes.

​
Provide feedback and continue conversations

Reply directly to cubic’s review comments (no @ mention needed) to: Continue the discussion:
  • “This would break our legacy API compatibility”
  • “What about error handling in this case?”
  • “Can you suggest an alternative approach?”
Provide feedback for learning:
  • “This is a false positive, Next.js handles this automatically”
  • “The rule is too strict for our use case”
  • “This doesn’t apply to React Server Components”
cubic will respond to your replies, maintaining the full context of the conversation thread.

​
Tips and best practices

  • Natural conversations: After cubic’s initial comment, just reply normally - no need to tag it again
  • Context awareness: cubic maintains the full thread context, understanding both the original suggestion and all previous replies
  • Be specific: More detailed questions get more helpful answers
  • Natural language: Write as you would to a teammate
  • Multi-turn discussions: Feel free to have back-and-forth conversations to refine suggestions or explore alternatives