Install any skill in seconds. Free to start, no credit card required.
Get Started Free →react/compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
Passed 7 of 16 test cases with the skill, and 3 of 16 without it.
and 7 more in the full report
8 fixed1 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I ran a review command with no arguments. `git diff HEAD -- compiler/crates/` returned an empty diff. What is the next exact git command step to check if changes were staged?
| Checked | Without skill | With skill |
|---|---|---|
| Executes git diff --cached -- compiler/crates/ as the fallback check for staged changes | Missed | Passed |
The instructions your model reads when the skill loads.
Review Rust compiler port code for correctness and convention compliance.
Arguments:
HEAD~3..HEAD, abc123). If omitted, reviews uncommitted/staged changes.Get the diff based on arguments:
git diff HEAD -- compiler/crates/ (uncommitted changes). If empty, also check git diff --cached -- compiler/crates/ (staged changes).abc123): git diff abc123~1..abc123 -- compiler/crates/HEAD~3..HEAD): git diff HEAD~3..HEAD -- compiler/crates/If no Rust changes found, report "No Rust changes to review." and stop.
Identify changed Rust files from the diff using git diff --name-only with the same ref arguments.
Launch the compiler-review agent via the Agent tool, passing it the full diff content. The agent will:
Report the agent's findings to the user.
test cases passed, vs 3 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.