self-review

Audit session changes for mistakes, missed requirements, and regressions.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill self-review-kitfunso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/kitfunso/omniskill/tree/main/skills/self-review
Command: npx skills add https://github.com/kitfunso/omniskill --skill self-review-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The self-review process helps identify mistakes, missing requirements, and regressions in the current session before delivery.

Core Features & Use Cases

  • Thoroughly inspects changes across all modified files and diffs to ensure correctness, completeness, and consistency.
  • Enforces quality and security checks by highlighting residual debugging code, unsafe patterns, and potential regressions.
  • Works across code, documentation, and configuration edits to verify wrap-up readiness and provide a clear audit trail.

Quick Start

Run the self-review to audit your latest changes and verify correctness before wrapping up.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I review session changes to catch missed requirements and regressions?

To review session changes for regressions and missed requirements, run an automated audit against all modified files and diffs. This inspects code, documentation, and configuration edits to verify correctness, completeness, and consistency before delivery.

What is the best way to check diffs for residual debugging code and unsafe patterns?

Checking diffs for residual debugging code and unsafe patterns requires a structured quality and security review. This process highlights potential regressions and unsafe patterns across all modified files to ensure wrap-up readiness and provide a clear audit trail.

How do I audit code and configuration changes before wrapping up a development session?

Auditing code and configuration changes before wrapping up involves inspecting all modified files and diffs. This structured review enforces quality and security checks to verify correctness, completeness, and consistency across all session edits.

Does automated diff review work for both documentation and configuration files?

Yes, automated diff review works for documentation and configuration files. The process thoroughly inspects changes across all modified files to ensure correctness, completeness, and consistency regardless of whether the edits are code, documentation, or configuration.

When do I need a structured review of my current session changes?

You need a structured review of current session changes during development, review, and wrap-up workflows. It satisfies quality checks, traceability, and risk mitigation by guiding structured review steps to catch mistakes and regressions before delivery.

How do I verify wrap-up readiness and traceability for recent code edits?

Verifying wrap-up readiness and traceability for recent code edits requires auditing all session changes. This process enforces quality and security checks across modified files and diffs to ensure correctness and provide a clear audit trail.