self-review

Verifies code changes through diff inspection, requirement verification, testing, and regression review.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/KISHORETAMIL03579/WEEKLY-RAG-BUILD --skill self-review-kishoretamil03579
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/KISHORETAMIL03579/WEEKLY-RAG-BUILD/tree/main/.gemini/skills/self-review
Command: npx skills add https://github.com/KISHORETAMIL03579/WEEKLY-RAG-BUILD --skill self-review-kishoretamil03579

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes are often declared complete immediately after implementation without verifying correctness, integration, or edge cases, leading to regressions, broken pipelines, and fabricated completion claims. This Skill enforces a mandatory self-review and verification cycle before any task is marked done. ## Core Features & Use Cases - Mandatory Verification Workflow: Enforces a staged pipeline from requirement understanding through diff inspection, requirement-by-requirement verification, integration review, edge-case analysis, testing, and regression checks. - Domain-Specific Reviews: Includes dedicated checklists for RAG pipelines, trace analysis, multi-worker concurrency, security, and documentation consistency. - Structured Final Report: Produces a standardized completion report with requirement status (PASS/PARTIAL/FAIL/NOT VERIFIED), test evidence, remaining risks (P0-P3), and an explicit final verdict. - Use Case: After fixing a retrieval bug in a RAG application, use this Skill to inspect the actual git diff, verify each requirement against runtime evidence, run regression tests, and produce an evidence-backed completion report instead of assuming the fix works. ## Quick Start Ask the AI to apply the self-review skill to verify the code change just implemented before declaring the task complete.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I verify a code change is actually correct before marking a task complete?

Follow a staged self-review workflow: inspect the actual git diff, verify each requirement against runtime evidence, run the project's tests, review integration and edge cases, then produce a completion report. Passing tests alone does not prove correctness.

What should a code self-review checklist include?

A thorough checklist covers requirement verification, git diff review, integration and side-effect analysis, edge cases, security review, concurrency behavior, automated and runtime tests, documentation consistency, and confirmation that no secrets or runtime artifacts were committed.

Does this self-review process work for RAG pipeline changes?

Yes, it includes a dedicated RAG review covering ingestion, chunking, embedding, vector storage, retrieval, reranking, generation, citations, and trace logging. It ensures a retrieval change does not break other pipeline stages.

Why does the workflow forbid declaring completion right after implementation?

Implementation only shows code was written, not that it works. The workflow requires evidence from diff inspection, tests, and runtime verification, and explicitly prohibits fabricating test results, trace IDs, or verification claims.

When should code changes be avoided during an analysis phase?

When a task specifies a zero-change observation phase, such as baseline trace analysis, the workflow requires recording issues without modifying code. Corrections are only made during the permitted correction phase to preserve baseline validity.