review-work

Analyze code changes for correctness, quality, and risk with a multi-pass review.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill review-work-juhwa-lee1023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-work
Source: https://github.com/Juhwa-Lee1023/x-for-github-copilot/tree/main/source/skills/review-work
Command: npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill review-work-juhwa-lee1023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After implementing changes, teams often struggle to determine if the work is correct, coherent with existing patterns, and safe to ship. This skill provides a repeatable, multi-pass review to identify correctness gaps, quality issues, and potential risks before handing work back.

Core Features & Use Cases

  • Correctness pass: verify that changes align with user intent and handle edge cases.
  • Quality pass: assess consistency with project conventions, documentation, and tests.
  • Risk pass: surface potential regressions, API changes, and deployment considerations.
  • Use Case: When you've implemented a feature, run this review to produce a prioritized list of issues and a ship/no-ship recommendation.

Quick Start

Run the three review passes on the latest changes to produce a prioritized list of findings and a ship/no-ship recommendation.

Frequently Asked Questions about review-work

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

FAQPage Schema
How do I perform a multi-pass code review for post-implementation changes?

A multi-pass code review analyzes new code changes across three phases: correctness verification, quality assessment against project conventions, and risk evaluation for potential regressions to produce a prioritized ship/no-ship recommendation.

What is the best way to assess code correctness and risk before deployment?

Assess code correctness and risk by running a structured review workflow that verifies edge cases, checks alignment with user intent, and surfaces API changes and deployment considerations into a prioritized risk register.

Can I use a structured workflow to review GitHub Copilot generated code?

Yes, you can review GitHub Copilot generated code by applying a deterministic review workflow that evaluates correctness, quality consistency, and deployment risks to guide reviewers through structured findings.

How does a multi-pass code review identify potential regressions?

A multi-pass code review identifies potential regressions during the risk pass by explicitly analyzing new changes for API modifications, deployment hazards, and coherence issues, aggregating them into a prioritized risk register.

Does post-implementation review work without external dependencies?

Post-implementation review works without external dependencies by utilizing a deterministic, structured workflow to analyze code changes and generate a ship/no-ship recommendation based purely on the provided codebase.

When do I need a ship/no-ship recommendation for code changes?

You need a ship/no-ship recommendation when you have implemented a feature and must determine if the work is correct, coherent with existing patterns, and safe to ship before handing it back for deployment.