agentsclimarketplace

Code review skill

Skill ChristinaAgent/OpenSkillBench/examples/code-review-skill

Benchmark, lint, and standardize reusable skills for AI coding agents.

Install
npx -y skills add ChristinaAgent/OpenSkillBench --skill code-review-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review code changes for correctness bugs, regressions, and missing tests before a pull request is merged.

SKILL.md

1.6 KB, as published. Nobody here has run it

Code Review Skill

Use this skill when the user asks for a code review.

Procedure

  1. Inspect the current diff and nearby code.
  2. Identify behavioral regressions, correctness bugs, security issues, and missing tests.
  3. Report findings first, ordered by severity.
  4. Include file and line references when available.
  5. Keep style-only comments out unless they hide a real maintainability risk.

Output Shape

Start with findings. If no findings are found, say that clearly and mention any remaining test gaps or residual risk.

Gives 0 of the 12 instructions most code review skills give

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06

  • push back with technical reasoning if wrongin 60 of 610, across 24 files
  • ask for clarification on unclear itemsin 51 of 610, across 16 files
  • fix critical issues immediatelyin 45 of 610, across 29 files
  • implement one item at a timein 45 of 610, across 11 files
  • group findings by severityin 44 of 610, across 43 files
  • verify feedback against the codebasein 42 of 610, across 8 files
  • dispatch a code reviewer subagentin 39 of 610, across 23 files
  • fix important issues before proceedingin 37 of 610, across 22 files
  • test each fix individuallyin 35 of 610, across 7 files
  • reply in github comment threadsin 33 of 610, across 5 files
  • check for security vulnerabilitiesin 31 of 610, across 27 files
  • factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

  • Omit style-only comments unless they hide maintainability risk

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.