skills.rest
congthang12312
congthang12312COMMUNITY
Explore all skills by this author →
GitHub

code-review

Enforce evidence-based review practices on pull requests before merge.

Updated Mar 19, 2026
Search Tags:#feedback#verification#quality-assurance#code-review#pull-request#edge-case
One-click install
npx skills add https://github.com/congthang12312/Sentinel-AI-test --skill code-review-congthang12312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/congthang12312/Sentinel-AI-test/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/congthang12312/Sentinel-AI-test --skill code-review-congthang12312

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review code changes for quality and compliance with standards, providing evidence-based feedback and protecting completion claims.

Core Features & Use Cases

  • Edge-case scouting before PR review to surface potential issues.
  • Evidence-based verification gates to prevent premature completion claims.
  • Structured feedback protocol to ensure concise, actionable reviews.

Quick Start

Review a recent PR by invoking the guided review flow and citing evidence and edge cases before 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 an evidence-based code review before merging a pull request?▼

To perform an evidence-based code review, enforce verification gates and edge-case scouting on pull requests before merge. This prevents premature completion claims by requiring structured feedback and cited evidence during the review process.

What is edge-case scouting in pull request reviews?▼

Edge-case scouting in pull request reviews is the process of identifying potential boundary issues and unhandled scenarios before merging. It surfaces hidden defects early by verifying code changes against unexpected inputs and execution paths.

How do I verify code quality and prevent premature completion claims?▼

You verify code quality and prevent premature completion claims by enforcing evidence-based verification gates across modules. This protocol requires validating implementation details and scouting edge cases before approving any merge or completion assertion.

Can I use structured feedback protocols for reviewing code changes across different modules?▼

Yes, you can apply structured feedback protocols to review code changes across modules. The protocol enforces concise, actionable reviews by guiding the identification of edge cases and citing evidence before merging pull requests.

When should I enforce verification gates during the software development lifecycle?▼

You should enforce verification gates after implementation, before merge, and when validating completion claims. This timing ensures edge-case scouting and evidence-based review practices are applied precisely when code quality must be verified.

What is the best way to provide concise and actionable feedback on a pull request?▼

The best way to provide concise feedback on a pull request is to follow a structured feedback protocol that cites evidence and identifies edge cases. This ensures reviews remain brutal, actionable, and focused on quality assurance.

Related Skills

Explore More Software Engineering Skills→
dthuy62dthuy62

ck:code-review

Review code changes for defects, security flaws, and requirement mismatches.

Community
Advanced
devs6186devs6186

land-and-deploy

Automate pull request merge, production deployment, and canary health verification.

Community
Advanced
ccfccf

llm-evaluation

Automate LLM evaluation with automated metrics, human feedback, and benchmarking.

Community
Advanced
tiweentiween

bmad-review-edge-case-hunter

Analyze code, specs, or diffs for unhandled edge cases and output a JSON report.

Official
Advanced