skills.rest
carrotwaxr
carrotwaxrCOMMUNITY
Explore all skills by this author →
GitHub

self-review

Review repository changes for bugs, style issues, and test coverage.

37|6|Updated Oct 10, 2025
Search Tags:#typescript#testing#code review#linting#pull-requests#diff-analysis#self-review
One-click install
npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill self-review-carrotwaxr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/carrotwaxr/peek-stash-browser/tree/main/.claude/skills/self-review
Command: npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill self-review-carrotwaxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers perform a thorough self-review of branch changes before creating a pull request by identifying bugs, style issues, failing tests, missing type checks, and gaps in test coverage to prevent regressions and blocked merges.

Core Features & Use Cases

  • Diff-driven guidance: Inspect changes between main and HEAD to understand scope and selectively apply relevant review guidance.
  • Automated checklist: Run and verify tests, linters, and TypeScript checks, and classify issues as blocking, should-fix, or note-for-later.
  • Skill orchestration: Invoke specialized best-practice skills based on changed paths (UI, server, GraphQL, Docker, tests) to surface targeted recommendations.
  • Use Case: A developer finishing a feature branch runs this review to catch lint errors, failing tests, performance issues, and inconsistent UI patterns before requesting a PR.

Quick Start

Run a self-review of the current branch against main, identify blocking issues and recommended fixes, and list tests or linters that must pass before creating a PR.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I run a self-review on my branch before creating a pull request?▼

Perform a pre-PR self-review by inspecting the diff between main and HEAD, running linters and TypeScript checks, and classifying issues as blocking, should-fix, or note-for-later.

What is the best way to catch missing test coverage and lint errors before submitting a PR?▼

Catch missing test coverage and lint errors by running an automated review checklist on your branch changes, invoking relevant best-practice skills per changed path, and verifying that tests pass.

Does this code review tool check TypeScript types and diffs for both client and server changes?▼

Yes, this code review tool checks TypeScript types and inspects diffs for client, server, test, Docker, and GraphQL changes by selectively applying targeted review guidance based on changed paths.

How are identified issues classified during a pre-PR code quality check?▼

During a pre-PR code quality check, identified issues are classified into three categories: blocking issues that prevent merges, should-fix items, and notes for later consideration.

Can I use this to run tests and linters automatically for my development branch?▼

Yes, you can use this to run and verify tests and linters automatically for your development branch, ensuring type checks pass and regressions are prevented before requesting a PR.

Related Skills

Explore More Software Engineering Skills→
ignissionignission
2

pre-push-review

Identify changed files since origin/main and run Codex review into a table.

Official
Intermediate
uesleinaschuesleinasch

unac-fix-blockers

Orchestrate fixes for blocking issues from code review reports.

Community
Advanced
do360nowdo360now

security-review

Detects project environment and delegates to specialized security sub-skills.

Community
Intermediate
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate