agentsclimarketplace
Sign in

Review

Skill kevinb361/agent-skills/skills/review

Perform a read-only review of code changes for concrete bugs, security risks, regressions, performance problems, and missing tests. Use for staged, unstaged, commit, branch, or pull-request diffs.From its SKILL.md

Install
npx -y skills add kevinb361/agent-skills --skill review

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.8 KB, 309 tokens by cl100k_base, as published. Nobody here has run it

Code review

Review only; do not edit files while this skill is active.

Scope

Determine the requested scope. With no explicit scope, inspect staged changes first, then unstaged changes, then the latest commit. For branch review, find the actual merge base rather than assuming a branch name.

Confirm the working directory before every Git command. Stop if there is no diff to review.

Method

  1. Read project instructions.
  2. Inspect the complete diff and changed-file list.
  3. Read enough surrounding implementation and tests to understand the changed behavior. Read full hand-written files when practical; do not waste context on generated files, lockfiles, or vendored code when a targeted inspection is sufficient.
  4. Trace callers, data boundaries, error paths, and state transitions affected by the change.
  5. Check tests for changed behavior, boundaries, and failure paths.
  6. Report only issues introduced or exposed by the reviewed change.

Prioritize correctness, security, data loss, concurrency, compatibility, resource leaks, operational failure modes, and meaningful performance regressions. Do not report formatting preferences or speculative concerns without a concrete failure scenario.

Findings

Order findings by severity. Each finding must include:

  • severity
  • path:line
  • the concrete failure or risk
  • why the change causes it
  • a specific remediation

If no material issue is found, say so and mention any verification gap that limits confidence. Do not claim that code is safe to merge solely because no issue was found.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

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.