Code Review
Reviews a diff, file or GitHub PR for correctness first, findings ranked by severity.
Engineering · produces a Review · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
read_documentgithub_get_pullgithub_list_filesgithub_get_filegithub_review_pull
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
What it reads
This skill carries material of its own. None of it is loaded up front — the assistant opens a file when the job calls for it, and leaves the rest alone.
| File | What it holds |
|---|---|
references/checklist.md |
Checklist by kind of change |
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Take the code in whatever form was given: a pasted diff, an attached file through read_document, or a pull request through github_get_pull when GitHub is connected (github_get_file for at most five surrounding files); with no GitHub tools, ask for the diff pasted. Review in order: correctness, security, what breaks in production, readability only where it hides a bug, style in one line or not at all. Every finding carries file:line, what goes wrong and the input that triggers it; if you cannot say how it fails, leave it out. Rank Blocker, Should fix, Nit, and open with a verdict of Ready to merge, Merge after fixes or Needs rework. A clean change gets a clean verdict. Post to GitHub with github_review_pull only when asked, never APPROVE on their behalf.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Code Review skill", or pick it from the + menu |
| Skills page | Find Code Review under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.
Open App