Skip to main content
Add issue context from GitHub Issues to make AI reviews understand your requirements, generate accurate PR descriptions and analyze if your code meets the acceptance criteria in the issue. GitHub Issues works through the cubic GitHub App you already installed, so there is no separate account to connect.

​
Setup

​
Enable GitHub Issues

  1. Navigate to integration settings.
  2. Open GitHub Issues and click Connect.
If cubic reports that it can’t access issues, accept the updated permissions for the cubic GitHub App in your GitHub organization settings, then try again.

​
Configure AI behavior

Toggle these options based on your workflow:
  • Use context when reviewing code - AI reviews check if code matches issue requirements
  • Show linked issue analysis in reviews - Post acceptance criteria assessment in PR review comments. When disabled, issue context still improves AI review quality but is not shown publicly. Requires “Use context when reviewing code” to be enabled
  • Use context when writing PR descriptions - Generate descriptions from the linked GitHub issue

​
How it works

cubic uses the issue GitHub links to your pull request. Link an issue the way you normally would on GitHub:
  • Add a closing keyword to the PR description, such as Fixes #123.
  • Link the issue from the Development section of the PR sidebar on GitHub.
For pull requests that target a branch other than the default branch, such as stacked PRs, GitHub doesn’t link issues from closing keywords. cubic reads the closing keywords in the PR description itself in that case, for issues in the same repository. The linked issue appears in the cubic PR sidebar. To change it, update the link on GitHub.
Issue content can appear in AI review comments and PR descriptions, which everyone who can see the pull request can read. cubic uses issues from the pull request’s own repository. It only uses an issue from another repository when that issue is public and an organization member opened the PR, because people who can read the pull request might not have access to the other repository.

​
Create GitHub issues from codebase scans

With GitHub Issues enabled, you can file codebase scan findings as GitHub issues, one at a time, in bulk, or automatically after each scan. Issues are created in the scanned repository. cubic only files findings in private repositories, because scan findings can include security issues that shouldn’t be disclosed publicly.

​
Best practices

  • Write clear acceptance criteria in the issue for better AI feedback
  • Use bullet points or numbered lists for requirements to enable automatic issue analysis
  • Include specific, testable criteria that cubic can verify in your code changes