skills.rest
Wakewell-Sleep-Solutions
Wakewell-Sleep-SolutionsOFFICIAL
Explore all skills by this author →
GitHub

code-review

Trigger formal code reviews and process feedback before merging to main.

Updated Aug 23, 2026
Search Tags:#workflow#feedback#diff#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/Wakewell-Sleep-Solutions/claude-skills-ecosystem --skill code-review-wakewell-sleep-solutions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Wakewell-Sleep-Solutions/claude-skills-ecosystem/tree/main/requesting-code-review
Command: npx skills add https://github.com/Wakewell-Sleep-Solutions/claude-skills-ecosystem --skill code-review-wakewell-sleep-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are critical gates that ensure technical accuracy and alignment with project goals before merging.

Core Features & Use Cases

  • Request structured reviews after each task or major feature to catch issues early.
  • Follow a standardized feedback loop (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to ensure actionable and traceable responses.
  • Apply ad-hoc reviews before merges or when responding to feedback from reviewers.

Quick Start

Summarize your changes and plan, then request a formal code-review and act on the reviewer's feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I request a structured code review before merging changes to main?▼

To request a code review, summarize your changes and plan, then trigger a formal review to validate technical accuracy before merging. This enforces a structured feedback workflow to ensure reproducible, high-quality outcomes.

What is the standard feedback workflow for processing pull request reviews?▼

The standard code review feedback workflow follows six steps: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This standardized loop ensures actionable and traceable responses to reviewer feedback.

When should I trigger an ad-hoc code review instead of a formal one?▼

Trigger ad-hoc code reviews before merges or when responding to feedback from reviewers. Formal reviews are requested after task completion or major feature implementation to catch issues early.

How does severity-based issue triage work during code reviews?▼

Severity-based issue triage during code reviews categorizes feedback by criticality to prioritize fixes. This structured triage ensures reproducible, high-quality outcomes by enforcing formal validation before merging to main.

Can I use this code review workflow for post-review revisions?▼

Yes, the code review skill processes feedback across post-review revisions. It covers requesting reviews and acting on feedback after task completion, major feature implementation, and subsequent reviewer revisions.

Related Skills

Explore More Software Engineering Skills→
aurora-atomsaurora-atoms

reviewer-rehearsal

Identify design risks and missing evidence in software changes for formal review.

Community
Advanced
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
riftzen-bitriftzen-bit

continuous-agent-loop

Automate continuous agent loops with quality gates, evals, and recovery controls.

Community
Advanced
richardnguyen0715richardnguyen0715

requesting-code-review

Automate pre-commit code review with security scans, quality checks, and auto-fixes.

Community
Advanced