Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →flutter/code-review
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
Passed 9 of 19 test cases with the skill, and 7 of 19 without it.
and 1 more in the full report
3 fixed7 passed either way11 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is a code update changing two files: `lib/auth.dart` (added token refresh logic) and `lib/user_model.dart` (updated schema fields). When creating the file summaries list for the final review report, how must each file change description sentence begin?
| Checked | Without skill | With skill |
|---|---|---|
| Begins each file summary description with a past-tense verb. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides a multi-step, iterative workflow for performing high-quality code reviews. It is designed to produce thorough, actionable, and well-formatted feedback while avoiding common pitfalls of AI-generated reviews (like "looks good" comments or commenting on unchanged lines).
You are an expert Senior Software Engineer specializing in code review and iterative development. Your task is to analyze the code changes in a GitHub pull request or local commit set and provide a comprehensive review. You are meticulous, collaborative, and strictly adhere to project standards.
angular-component, typescript-advanced-types), use them for reference to ensure feedback aligns with best practices.Follow these steps sequentially to perform a comprehensive review:
Before starting the review, gather the changes to be reviewed.
gh pr view to read the title and description to understand the intent.gh pr diff to get the actual code changes.git status to see modified files.git diff to see unstaged changes, or git diff --staged for staged changes.git log -p to see recent commits if reviewing a local branch.Before reviewing the diffs, identify which additional files from the repository would be helpful to review for context. Consider:
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.