self-review

Validate code against a feature plan before pull requests.

Updated Feb 14, 2026

Search Tags:#quality-assurance #code-review #pull-request #development-workflow #self-review #feature-plan #pre-pr

Ready to run

npx skills add https://github.com/Suniljit/personal-toolkit --skill self-review-suniljit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/self-review
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill self-review-suniljit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review your own code against a feature plan before creating a PR. It helps identify gaps between implementation and intended design, ensuring quality and alignment.

Core Features & Use Cases

Resolve inputs: require the feature plan doc (and optionally a ticket + feature brief) and do not proceed until provided.
Read the plan: extract summary, design decisions, key files, implementation phases, edge cases, and testing requirements.
Explore the relevant code: verify key files exist, read code to understand flow, trace imports and references, and discover related files.
Cross-check and deliver the review: produce a structured checklist mapping plan items to code changes, flag gaps or low-confidence areas before PR.

Quick Start

Provide the feature plan doc path and optional ticket/brief, then run the self-review against the current branch.

Frequently Asked Questions about self-review

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

FAQPage Schema

How do I review my code against a feature plan before creating a PR?▼

To review code against a feature plan before a PR, you provide the plan document and optional ticket context so the tool can diff current changes against expected design decisions, implementation phases, and edge cases.

What is a pre-PR self-review in a plan-driven development workflow?▼

A pre-PR self-review is a validation step that diffs current branch work against feature plan expectations, flagging gaps in key files, design decisions, and testing requirements before submitting a pull request.

Can I use a feature brief and ticket context for code review validation?▼

Yes, you can supply an optional feature brief and ticket context alongside the required feature plan document to provide deeper validation context when cross-checking implementation phases and edge cases.

How do I check if my pull request implementation covers all edge cases from the plan?▼

You can check pull request implementation coverage by extracting testing requirements and edge cases from the feature plan, then mapping them against your code changes to identify gaps or low-confidence areas.

What's the best way to validate design decisions in my current branch before a PR?▼

The best way to validate design decisions is to explore relevant code by tracing imports and references, ensuring your current branch implementation aligns with the key files and design decisions extracted from the feature plan.