code-review

Identify and document bugs, risks, and verification gaps in code changes.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/seshxn/ai-swarm --skill code-review-seshxn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/seshxn/ai-swarm/tree/main/skills/code-review
Command: npx skills add https://github.com/seshxn/ai-swarm --skill code-review-seshxn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes for correctness, maintainability, risk, and missing verification to ensure code quality and safer deployments.

Core Features & Use Cases

  • Structured findings: captures priority, evidence, and recommendations for each issue.
  • Verification alignment: ensures test gaps and verification steps are identified.
  • Collaboration support: guides reviewers to communicate issues clearly to developers.

Quick Start

Review a pull request and generate a code-review findings report.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically identify bugs and risks in a pull request?

Automated code review identifies bugs and risks in pull requests by analyzing changes for correctness and maintainability. It documents specific issues, captures priority levels, and provides evidence to ensure safer deployments and verifiability.

What is structured code review and how does it document verification gaps?

Structured code review systematically evaluates code changes to document bugs, risks, and missing verification steps. It ensures findings include actionable recommendations, priority levels, and test gaps to improve overall maintainability.

Can I use automated code review for merged changes and swarm reviews?

Yes, automated code review applies to pull requests, merged changes, and swarm reviews across software projects. It focuses on correctness, maintainability, and verifiability to ensure ongoing code quality after integration.

What is the best way to document test gaps and missing verification during code changes?

The best way to document test gaps is through structured code review findings that explicitly capture missing verification steps. This ensures test coverage issues are communicated clearly to developers with supporting evidence and actionable recommendations.

Does structured code review work without external dependencies or components?

Structured code review works without external dependencies or components, operating as a standalone process. It focuses on identifying correctness, maintainability, and verifiability issues directly from the code changes provided.