Review code
with agent skills.

A useful code review connects a specific change to a concrete failure or unmet requirement. These skills help with requesting a review, inspecting a patch and working through the findings.

Filter these skills by stack and access

Choose a skill

Distinguish reviewing code from preparing a review request or responding to feedback. Choose guidance that fits the change and your stack. Keep the reviewer independent of the implementation when the risk warrants it.

Explore the review loop kit

Before you install

Name the base and head revision, the intended behavior and the areas that changed. Ask for findings with file locations, impact and supporting evidence. Say explicitly whether the task is read-only or includes making fixes.

Open a listing to read its source, access labels and review evidence before copying its install command. The automated scan covers SKILL.md, not referenced files or runtime behavior. Read the review limits.

Skills for this task

15 available skills, listed A to Z. Task labels help narrow the choice; they do not establish fit for your project.

Check the result

  1. 01

    Check each finding against the current diff and its callers. Separate defects from style preferences.

  2. 02

    Reproduce important failures where safe, and verify the proposed fix addresses the cause.

  3. 03

    Rerun affected checks after changes. Resolve review threads only when the finding has been addressed or a decision is recorded.

Example: review a pagination change

Use this illustrative brief when a change adds pagination to an existing list. Replace the revisions, file paths and requirements with your own. This is a starting point for a review, not a report from a tested project.

Review the diff from BASE_SHA to HEAD_SHA without editing files. The list must show each matching item once, preserve the selected filter when moving between pages, and handle an empty result. Trace the changed pagination code and its callers. Report defects with a file and line, the input or sequence that triggers them, and the expected versus actual behavior. Separate confirmed findings from checks you could not perform. Do not run commands or contact services without permission.

What a useful finding would contain

For example, a reviewer might suspect that changing the filter leaves the page number unchanged. To confirm it, they would need to show the state transition in code or reproduce a case where page 4 becomes empty even though the new filter has results on page 1. A statement such as “pagination may be broken” is not enough.

What to check after a fix

Repeat the reported sequence. Check first and last pages, empty results, filter changes and repeated navigation. Record the commands or manual steps actually run. Passing this example does not establish that every pagination path is correct.