self-reviewer

Detects and fixes code issues before pull request creation through layered self-review.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill self-reviewer-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-reviewer
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/self-reviewer
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill self-reviewer-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches defects, scope creep, and hygiene issues in your changes before a pull request is opened, reducing review round-trips and avoiding the blind spots of reviewing your own work in the same context. ## Core Features & Use Cases - Machine Checks First: Runs tools/self_review_check.py and CJK markdown auto-formatting to block PRs with merge conflict markers, oversized files, or formatting warnings. - Perspective-Based Diff Review: Walks the diff through a checklist covering correctness, duplication, naming, backward compatibility, security, error handling, tests, YAGNI scope, and documentation consistency. - Fresh-Context Pre-PR Review: Invokes a separate code-review skill with --pre-pr on high-risk or code diffs so CONFIRMED findings are fixed before the PR exists, then runs a mandatory post-PR Layer 1 review. - Use Case: Before opening a PR that touches authentication hooks, run this skill to machine-check the branch, self-review the diff, get a fresh-context review verdict, and record the results in the PR body. ## Quick Start Ask the AI to run a self-review and check everything before creating the pull request for the current branch.

Frequently Asked Questions about self-reviewer

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

FAQPage Schema
How do I self-review code before creating a pull request?▼

Run the machine check script first, then verify the diff scope against the task, review changes across perspectives like correctness and security, and confirm branch hygiene. High-risk diffs also require a fresh-context review before the PR is opened.

What checks should run before opening a GitHub PR?▼

Run automated checks for merge conflict markers and oversized files, auto-format changed Markdown files, verify no out-of-scope files are included, and ensure the working tree is clean with all commits pushed.

Does this self-review workflow use external AI reviewers?▼

No, the review is completed entirely by the AI assistant itself. External reviewers like Copilot or Gemini are explicitly not used; a project-local code-review skill handles the fresh-context review layers instead.

When can the pre-PR fresh-context review be skipped?▼

It can be skipped only when the diff contains data or state files exclusively, detected via the diff-type script. In that case the PR body must note the skip reason in one line.

Why does self-review fail to catch my own mistakes?▼

Same-context self-review misses self-caused errors at a high rate, so the workflow adds a fresh-context review pass that treats the diff as a third-party PR. Confirmed critical and warning findings must be fixed before proceeding.