self-review

Identify and document PR issues across code quality, security, and testing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MoneyForest/dotfiles --skill self-review-moneyforest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/MoneyForest/dotfiles/tree/main/claude/skills/self-review
Command: npx skills add https://github.com/MoneyForest/dotfiles --skill self-review-moneyforest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Self-review checklists help developers objectively assess code after implementation, ensuring quality, security, performance, testing, and design patterns before PRs.

Core Features & Use Cases

  • Comprehensive criteria for code quality, security, performance, testing, and design patterns.
  • Workflow applicability after feature completion, before PR submission, or during code reviews.
  • Use Case: A developer audits a new module to verify it meets internal standards prior to creating a PR.

Quick Start

Run the self-review checklist on your latest PR to identify and log issues before requesting feedback.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I do a self-review on a pull request before submitting it?▼

A pull request self-review involves running a structured checklist to identify and document issues across code quality, security, performance, testing, and design patterns before requesting feedback.

What criteria should I check during a code review for security and performance?▼

Code review criteria for security and performance should include verifying design patterns, assessing potential vulnerabilities, and documenting testing gaps to ensure the implementation meets internal standards.

Can I use a language-agnostic checklist for post-implementation code audits?▼

Yes, you can apply a language-agnostic checklist post-implementation to objectively audit a new module and verify it satisfies structured criteria for reviewer readiness.

What is the best way to minimize PR review delays?▼

The best way to minimize PR review delays is to perform a comprehensive self-review after feature completion, logging issues across code quality and testing before PR submission.

When do I need to apply a self-review checklist in my development workflow?▼

You need to apply a self-review checklist after feature completion and before PR submission, ensuring your code meets objective standards for quality and security during the review phase.