skills.rest
Kevin-Liu-01
Kevin-Liu-01COMMUNITY
Explore all skills by this author →
Website𝕏@kevskgsGitHub

plan-mode-review

Generate a structured pre-change review checklist covering architecture, code quality, tests, and performance.

16|3|Updated May 5, 2026
Search Tags:#planning#architecture#performance#documentation#quality-assurance#code-review#tests
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill plan-mode-review-kevin-liu-01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-mode-review
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/plan-mode-review
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill plan-mode-review-kevin-liu-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A structured review pass that catches issues before they ship, guiding teams through architecture, code quality, tests, and performance.

Core Features & Use Cases

  • Architecture review to validate patterns and ensure safe changes.
  • Code quality checks to enforce style, maintainability, and readability.
  • Tests and performance considerations to prevent regressions and bottlenecks.
  • Use Case: planning a feature, preparing a PR, or assessing user-shared code for quality and safety.

Quick Start

Initiate the plan-mode-review checklist on a feature branch before opening a PR.

Frequently Asked Questions about plan-mode-review

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

FAQPage Schema
What is a pre-ship code review checklist?▼

A pre-ship code review checklist is a structured evaluation that catches issues before changes ship by scrutinizing architecture, code quality, tests, observability, and performance.

How do I review architecture and code quality before opening a PR?▼

Review architecture and code quality before a PR by applying a multi-section checklist that validates patterns, enforces style, and ensures readability and safe changes.

What's the best way to plan a feature to prevent regressions and performance bottlenecks?▼

The best way to plan features and prevent regressions is to run a structured pre-change review evaluating tests and performance considerations alongside architecture and documentation.

Does this pre-change review work for assessing user-shared code?▼

Yes, this pre-change review works for assessing user-shared code by scrutinizing it for architecture, code quality, tests, and performance to ensure quality and safety.

Can I use a structured checklist for pre-PR reviews on a feature branch?▼

Yes, you can use this structured checklist for pre-PR reviews by initiating the evaluation on a feature branch to enforce pre-ship checks and observability criteria.

Related Skills

Explore More Software Engineering Skills→
Kord96Kord96

publish

Push the current git branch to origin with optional draft PR and Codex review.

Community
Intermediate
CODE-SAURABHCODE-SAURABH
2

land-and-deploy

Merge approved pull requests and verify production health after deployment.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
atournayreatournayre

orchestrator:validate

Run PHPStan, PSR-12, and security checks on PHP projects.

Community
Intermediate