Code review
Reviews a pull request for bugs, security issues and missing tests, sorted by severity.
A thorough review before code gets merged.
When to use
- Before merging a pull request.
- For code written by another bot or an AI.
Needs
- The diff or a link to the pull request (for example via GitHub).
- Optional: the goal of the change and the project’s rules.
Steps
- Read the description and the whole diff before commenting.
- Look for logic bugs first, then security issues (input handling, permissions, secrets in code).
- Check that new logic is tested and the failure cases are covered.
- Note readability and style last, and only when it matters.
- Suggest a concrete fix for every finding.
Check before answering
- Every finding names file and line.
- Findings are sorted by severity: blocking, important, minor.
- Matters of taste are never marked as blocking.
Output
A short verdict (merge, merge after fixes, do not merge), then the findings by severity.
Limits
- Comment only; do not merge or push yourself.
- Do not repeat secrets found in the code, only point to where they are.
SKILL.md
View file
---
name: code-review
description: "Use this skill when the user wants a pull request, diff or code snippet reviewed."
---
# Code review
A thorough review before code gets merged.
## When to use
- Before merging a pull request.
- For code written by another bot or an AI.
## Needs
- The diff or a link to the pull request (for example via GitHub).
- Optional: the goal of the change and the project’s rules.
## Steps
1. Read the description and the whole diff before commenting.
2. Look for logic bugs first, then security issues (input handling, permissions, secrets in code).
3. Check that new logic is tested and the failure cases are covered.
4. Note readability and style last, and only when it matters.
5. Suggest a concrete fix for every finding.
## Check before answering
- Every finding names file and line.
- Findings are sorted by severity: blocking, important, minor.
- Matters of taste are never marked as blocking.
## Output
A short verdict (merge, merge after fixes, do not merge), then the findings by severity.
## Limits
- Comment only; do not merge or push yourself.
- Do not repeat secrets found in the code, only point to where they are.
How to use the skill
- Create a folder
code-reviewand save the file in it as SKILL.md. - Add the folder to your Grok bot or paste the content into a new conversation.
- Test the skill with a sample task before you use it regularly.