requesting-code-review

Guide engineers through a structured code self-review before merging.

3|Updated Jan 22, 2026

Search Tags:#documentation #checklist #quality-check #code-review #software-engineering #pull-request

Ready to run

npx skills add https://github.com/falconnt/windsurf-skills --skill requesting-code-review-falconnt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/falconnt/windsurf-skills/tree/main/requesting-code-review
Command: npx skills add https://github.com/falconnt/windsurf-skills --skill requesting-code-review-falconnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured self-review protocol to catch issues early before merging, reducing bugs and rework.

Core Features & Use Cases

Structured review workflow: guides reviewers through code quality, architecture, testing, and documentation checks.
Consistent output: produces a standardized review report suitable for sharing with teammates and stakeholders.
Before-merge governance: ensures plans, requirements, and risk considerations are addressed prior to integration.

Quick Start

After implementing a major feature, trigger this Skill to generate a comprehensive review outline and documented findings based on your changes.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema

How do I perform a structured code review before a pull request?▼

A structured code review before a pull request involves running through a checklist covering code quality, architecture, testing, and documentation to catch issues early. This skill guides you through this self-review protocol to ensure production readiness before merging.

What is a self-review checklist for software engineering merges?▼

A self-review checklist for software engineering merges is a protocol verifying code quality, architecture, testing, and documentation. It provides a structured workflow to catch issues early before integration, reducing bugs and rework.

How do I ensure production readiness after implementing a major feature?▼

To ensure production readiness after implementing a major feature, trigger a structured self-review to generate a comprehensive review outline. This enforces a checklist covering plans, requirements, and risk considerations prior to integration.

Can I generate a standardized review report for my teammates before merging?▼

Yes, you can generate a standardized review report for teammates by applying a structured review workflow. This skill produces consistent output documenting code quality, testing, and architecture findings suitable for sharing with stakeholders.

Does this code review checklist work for refactoring tasks?▼

Yes, this code review checklist works for refactoring tasks. It applies to completing major features, post-implementation checks, and refactors across software projects to ensure architecture and code quality before merging.