code-quality-review

Review completed code for quality problems and behavior-preserving simplifications.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill code-quality-review-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-review
Source: https://github.com/OrestesK/pi/tree/main/skills/code-quality-review
Command: npx skills add https://github.com/OrestesK/pi --skill code-quality-review-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies accidental complexity, structural weaknesses, maintainability risks, and AI-generated code slop without turning a quality review into a cosmetic style pass or unauthorized editing session.

Core Features & Use Cases

  • Behavior-Preserving Review: Traces changed behavior through callers, callees, tests, contracts, side effects, and failure paths before proposing simplifications.
  • Structural Analysis: Evaluates simplicity, ownership, architecture, types, contracts, proof quality, and applicable operational or runtime concerns.
  • Validated Findings: Reports only concrete, reachable issues with evidence, impact, a smallest safe direction, and a confidence level.
  • Controlled Fix Mode: Supports explicitly authorized fixes while preserving manager-workflow approval, scope, staged validation, and post-change verification.
  • Use Case: Ask for a deep review of a completed feature to determine whether its wrappers, fallback branches, and cross-layer plumbing can be removed without changing its behavior.

Quick Start

Ask the code-quality-review skill to inspect the current change set for behavior-preserving simplifications and return a validated review verdict.

Frequently Asked Questions about code-quality-review

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

FAQPage Schema
Does a behavior-preserving code review support explicitly authorized fixes for identified technical debt?

A behavior-preserving code review supports explicitly authorized fixes through a controlled mode. This mode maintains manager-workflow approval, enforces staged validation, and requires post-change verification before applying any safe direction fixes to technical debt.

What is the best way to detect accidental complexity and AI-generated code slop in a codebase?

Detecting accidental complexity and AI-generated code slop requires structural analysis of implementation and architecture. A behavior-preserving review evaluates ownership, types, and contracts to report only reachable issues with concrete evidence and impact.

How to perform a deep code review on a completed feature to determine if wrappers and fallback branches can be removed?

Perform a deep code review by tracing changed behavior through failure paths and side effects. This structural analysis identifies unnecessary wrappers and fallback branches, proposing the smallest safe direction for removal while ensuring behavior preservation.

Can I use a code review process to safely simplify software architecture and remove cross-layer plumbing?

You can simplify software architecture by applying evidence-based scope control during a code review. The process traces behavior across cross-layer plumbing to validate findings and ensure any architectural simplification strictly preserves the original behavior.

Does a behavior-preserving code review support explicitly authorized fixes for identified technical debt?

A behavior-preserving code review supports explicitly authorized fixes through a controlled mode. This mode maintains manager-workflow approval, enforces staged validation, and requires post-change verification before applying any safe direction fixes to technical debt.