Skills are included when you set up cubic in your coding agent. See Coding agent integration for setup instructions.
Best prompts to start with
These prompts cover the workflow most teams use every day:| Prompt | Best time to use it | What happens |
|---|---|---|
"review my code" | Before you commit | Runs a local cubic review through your coding agent |
"loop until clean" | When you want the agent to keep iterating | Re-runs local review, fixes issues, and repeats until the local pass is clean or the loop stops |
"check cubic comments" | After cubic reviews a PR on GitHub | Fetches unresolved review comments, fixes worthwhile issues, commits, pushes, and resolves handled threads |
"how does auth work?" | Before changing unfamiliar code | Uses cubic’s codebase context to explain the system |
"what does this team care about in reviews?" | When writing code for a new repo | Surfaces team coding patterns and conventions |
Built-in skills
| Skill | Activates when | What it does |
|---|---|---|
| Check PR comments | Working on a PR branch, saying “check cubic comments”, “fix cubic issues”, or “check PR comments” | Fetches unresolved cubic review comments, autonomously fixes worthwhile issues, commits and pushes changes, and resolves handled threads. |
| Run review | Saying “review my code” or doing a pre-commit check | Runs a local cubic AI code review via the CLI and groups issues by priority. Requires the cubic CLI. |
| Codebase context | Asking “how does X work?” or questions about architecture | Queries the cubic AI Wiki to provide architectural context about your codebase. |
| Review patterns | Writing or reviewing code | Pulls team-specific review learnings to apply your team’s coding conventions and preferences. |
| Cubic loop | Saying “loop until clean” or “keep reviewing” | Iteratively runs cubic reviews, fixes issues, and re-reviews until clean or a max iteration count is reached. |
Use the prompts by stage
- Before you push
Ask your coding agent to
"review my code"or"loop until clean"to catch obvious issues early. - On an open pull request
Ask
"check cubic comments"after cubic finishes the GitHub review. The agent will fetch all unresolved threads, analyze them, and fix only issues that are real and worth addressing. It will then push the changes and automatically resolve the handled threads. - When learning the codebase
Ask questions like
"how does auth work?","where is rate limiting handled?", or"what does this team care about in reviews?".
AGENTS.md / CLAUDE.md guidance, see Local CLI review.
Slash commands
If you prefer explicit commands, use these:| Command | Description |
|---|---|
/cubic-run-review [flags] | Run a local cubic AI code review on uncommitted changes or branch diff |
/cubic-comments [pr-number] | Show cubic’s review comments on the current PR (auto-detects branch) |
/cubic-wiki [page-name] | Browse AI-generated codebase documentation |
/cubic-scan [scan-id] | View codebase security scan results and issues |
/cubic-learnings [learning-id] | Show team code review patterns and preferences |