agentsclimarketplace
Sign in

Code review excellence

Skill AravindS-Wick/aravindhan-skills/skills/library/code-review-excellence

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.From its SKILL.md

Install
npx -y skills add AravindS-Wick/aravindhan-skills --skill code-review-excellence

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 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.

SKILL.md

1.4 KB, 221 tokens by cl100k_base, as published. Nobody here has run it

Code Review Excellence

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

Use this skill when

  • Reviewing pull requests and code changes
  • Establishing code review standards
  • Mentoring developers through review feedback
  • Auditing for correctness, security, or performance

Do not use this skill when

  • There are no code changes to review
  • The task is a design-only discussion without code
  • You need to implement fixes instead of reviewing

Instructions

  • Read context, requirements, and test signals first.
  • Review for correctness, security, performance, and maintainability.
  • Provide actionable feedback with severity and rationale.
  • Ask clarifying questions when intent is unclear.
  • If detailed checklists are required, open resources/implementation-playbook.md.

Output Format

  • High-level summary of findings
  • Issues grouped by severity (blocking, important, minor)
  • Suggestions and questions
  • Test and coverage notes

Resources

  • resources/implementation-playbook.md for detailed review patterns and templates.

What ships with it: 1 file

13.1 KB alongside SKILL.md

resources/

Gives 0 of the 12 instructions most code review skills give in 221 tokens

Counted across 668 of the 814 authors here whose files we hold, read 2026-09-06

  • Provide technical reasoning when pushing backin 84 of 668, across 70 files
  • Fix critical issues immediatelyin 77 of 668, across 60 files
  • Dispatch a code reviewer subagentin 76 of 668, across 59 files
  • Fix important issues before proceedingin 73 of 668, across 56 files
  • Ask for clarification on unclear itemsin 68 of 668, across 56 files
  • Verify feedback against codebase before implementationin 66 of 668, across 55 files
  • Implement fixes one at a timein 64 of 668, across 53 files
  • Test each fix individuallyin 62 of 668, across 51 files
  • Restate technical requirements in own wordsin 57 of 668, across 46 files
  • Reply to inline comments in the specific threadin 51 of 668, across 40 files
  • Note minor issues for laterin 49 of 668, across 34 files
  • Group findings by severityin 48 of 668, across 47 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.