code-review

Review code changes for security, correctness, and performance issues.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill code-review-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/code-review
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill code-review-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers catch security issues, logic bugs, performance regressions, and maintainability problems during pull request or merge request reviews, so code quality is consistent and release risk is lower.

Core Features & Use Cases

  • Structured review checklist: Evaluates security, performance, correctness, maintainability, testing, accessibility, and documentation.
  • Severity-based feedback: Classifies findings as Critical, Major, Minor, or Nitpick so blocking issues are obvious.
  • Three-pass review process: Guides reviewers from architecture-level assessment to detailed line-by-line analysis and edge-case hardening.
  • Example use cases: Review a backend API change for injection risks, assess a frontend change for re-render or accessibility problems, or train new team members on a consistent review standard.

Quick Start

Ask the assistant to review your pull request diff using the code-review checklist and return severity-labeled findings with concrete fix suggestions.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request for security and performance issues?

To review a pull request for security and performance issues, apply a structured checklist covering correctness, maintainability, and testing, then classify findings by severity to highlight blocking problems.

What is the best way to structure code review feedback for a merge request?

The best way to structure code review feedback is by classifying findings as Critical, Major, Minor, or Nitpick, ensuring blocking issues are obvious and providing concrete fix suggestions for the merge request.

How does a multi-pass code review process work for finding logic bugs?

A multi-pass code review process works by guiding reviewers from architecture-level assessment to detailed line-by-line analysis and edge-case hardening, effectively catching logic bugs and maintainability problems.

Can I use an automated code review checklist for backend API changes?

Yes, you can use an automated code review checklist for backend API changes to assess injection risks, verify testing coverage, and evaluate documentation as part of your team review workflow.

Does structured code review work for training new team members on review standards?

Yes, structured code review works for training new team members by applying a consistent review checklist across pull requests, teaching them to identify severity levels and provide structured feedback.