skills.rest
boparaiamrit
boparaiamritCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Provides a structured, evidence-based code review process for pre-merge quality checks.

5|1|Updated Feb 7, 2026
Search Tags:#security#maintainability#best-practices#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill code-review-boparaiamrit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/boparaiamrit/skills-by-amrit/tree/main/skills/code-review
Command: npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill code-review-boparaiamrit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catch issues before they cascade by enforcing a structured, evidence-based review that improves software quality and safety.

Core Features & Use Cases

  • Checklist-based Review: A guided, repeatable process covering correctness, security, performance, and maintainability.
  • Evidence & Documentation: Requires rationale, tests, and artifacts to accompany changes.
  • Use Case: Before merging a feature branch, run a systematic review to ensure no regressions are introduced and that the change is well-supported.

Quick Start

Review the latest PR with the standard checklist to ensure readiness for merging.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a systematic code review before merging a pull request?▼

A structured code review catches issues early by enforcing an evidence-based process covering correctness, security, performance, and maintainability. It requires collecting rationale, tests, and artifacts to ensure changes align with quality standards and prevent regressions before merging.

What is the best way to ensure code maintainability and security during a pull request review?▼

Use a checklist-based review process to systematically assess security and maintainability alongside performance and correctness. This guided approach requires rationale, tests, and artifacts to accompany changes, ensuring software quality and safety before integration.

Can I use a checklist-driven workflow to review bug fixes and refactoring branches?▼

Yes, this structured review process applies to feature branches, bug fixes, and refactors across software projects. It implements a checklist-driven workflow with mandatory evidence collection to validate correctness, security, performance, and maintainability.

Does the code review process require test validation and documentation?▼

Yes, the review process explicitly requires test validation and documentation. It implements guidance to validate tests, check documentation, and ensure changes align with quality standards through mandatory evidence collection and clear decision points.

Why should I collect evidence and rationale during a code review?▼

Collecting evidence and rationale catches issues before they cascade by enforcing an evidence-based review that improves software quality and safety. It requires rationale, tests, and artifacts to accompany changes, preventing regressions and ensuring changes are well-supported.

Related Skills

Explore More Software Engineering Skills→
shaun0927shaun0927

quality-check

Identify and remediate code quality and security issues via checklist-driven reviews.

Community
Advanced
DevelonautDevelonaut
3

merge-pr

Verify CI checks, detect conflicts, and squash-merge approved pull requests.

Community
Advanced
CursorTouchCursorTouch
6.7k

windows-mcp-tool-tester

Generate and execute automated test cases for Windows-MCP tools.

Official
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced