skills.rest
lushly-dev
lushly-devOFFICIAL
Explore all skills by this author →
GitHub

do-review

Review code changes across correctness, security, testing, and performance dimensions.

4|1|Updated Dec 30, 2025
Search Tags:#git#developer tools#quality assurance#code review#pull request#self review
One-click install
npx skills add https://github.com/lushly-dev/afd --skill do-review-lushly-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-review
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/do-review
Command: npx skills add https://github.com/lushly-dev/afd --skill do-review-lushly-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring code quality and consistency before commits or merges, whether for self-review or pull requests.

Core Features & Use Cases

  • Self-Review: Analyze your uncommitted code against defined quality dimensions.
  • Pull Request Review: Provide structured, research-grounded feedback on incoming PRs.
  • Use Case: Before committing a new feature, run a self-review to catch potential bugs and style issues. For a teammate's PR, use the skill to ensure it meets correctness, security, and performance standards.

Quick Start

Run /do-review to start a self-review of your current changes.

Frequently Asked Questions about do-review

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

FAQPage Schema
How do I review my uncommitted code changes before a git commit?▼

To review uncommitted code changes, you can run a self-review to analyze your work against correctness, security, testing, performance, readability, and documentation dimensions before committing.

Can I use this to review an external pull request for correctness and security?▼

Yes, you can review an external pull request by fetching the PR context and applying a multi-dimension checklist to generate structured feedback categorized as BLOCKER, IMPROVEMENT, or PRAISE.

What is structured code review feedback and how does it categorize issues?▼

Structured code review feedback organizes identified issues into BLOCKER, IMPROVEMENT, or PRAISE categories, ensuring code quality and consistency by evaluating changes across multiple dimensions like security and performance.

What's the best way to ensure code quality for a teammate's pull request?▼

The best way to ensure code quality is to perform a pull request review that applies a multi-dimension checklist covering correctness, security, testing, performance, readability, and documentation to generate structured feedback.

What dimensions are checked during a pull request review?▼

A pull request review checks code changes across six dimensions: correctness, security, testing, performance, readability, and documentation, generating structured feedback to ensure quality before merges.

Related Skills

Explore More Software Engineering Skills→
kurkokurko
14

code-review

Generate complete verbatim code reviews for pull requests, diffs, and uncommitted Git changes.

Community
Advanced
RobbyMo81RobbyMo81

prepare-pr

Rebase GitHub pull requests onto main, fix review findings, and run build gates.

Community
Advanced
bitwisecookbitwisecook
59

irule-fix

Fix Tcl iRules by iteratively applying LSP diagnostics and automated corrections.

Community
Intermediate
ZendevveZendevve
20

mcaf-formatting

Format code using repository canonical formatter and linter commands.

Community
Intermediate