skills.rest
freema
freemaCOMMUNITY
Explore all skills by this author →
Website𝕏@GraslTGitHub

code-review

Structure code review feedback with a three-part sandwich method.

3|Updated Feb 11, 2026
Search Tags:#blockers#code-review#pull-request#tone-guidelines#review-framework#nitpicks
One-click install
npx skills add https://github.com/freema/ai-skills --skill code-review-freema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/freema/ai-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/freema/ai-skills --skill code-review-freema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves inconsistent, unstructured feedback in code reviews by providing a repeatable, structured workflow.

Core Features & Use Cases

  • Sandwich Method: Top Slice, Filling, Bottom Slice, ensuring a clear sequence for feedback.
  • Clear blockers vs. nitpicks: separates issues that block merging from minor notes.
  • Consistent tone and guidance: tone guidelines ensure direct, honest, and constructive feedback.

Quick Start

Apply the sandwich method when reviewing code: start with praise, present blockers, then finish with a clear verdict.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I structure pull request feedback to be clear and motivating?▼

Structure pull request feedback using a sandwich method: start with positive observations, present critical blockers in the middle, and finish with a clear verdict. This ensures code reviews remain consistent, direct, and constructive.

What is the best way to separate blockers from nitpicks in a code review?▼

Separating blockers from nitpicks in a code review involves categorizing merge-blocking issues apart from minor notes. This structured approach prevents merge delays and keeps feedback focused on critical changes.

How do I maintain a consistent tone when reviewing code across different pull requests?▼

Maintain a consistent tone in code reviews by applying enforced tone guidelines that ensure feedback is direct, honest, and constructive. This repeatable workflow eliminates unstructured or harsh comments across pull requests.

Can this review framework work for merge requests and code diffs outside of GitHub?▼

Yes, this review framework applies to pull requests, merge requests, and code diffs across software projects. The structured three-part process and tone guidelines are platform-agnostic for any code review workflow.

What should a structured code review workflow include to avoid unstructured feedback?▼

A structured code review workflow should include a three-part process—praise, critical blockers, and verdict—plus tone guidelines. This enforces a clear sequence for feedback and concrete examples for consistency.

Related Skills

Explore More Software Engineering Skills→
managedcodemanagedcode
4

mcaf-code-review

Audit pull request readiness for code, tests, and documentation.

Official
Intermediate
daominahdaominah

reviewing-code-and-pr

Review code changes and pull requests for business fit, quality, and security.

Community
Intermediate
roycolumbia-coderoycolumbia-code

gsd-ship

Automates GitHub pull request creation, review triggering, and merge tracking.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic