code-review-refactor

Review code and refactor guidance with evidence-backed, severity-classified findings.

Updated May 6, 2026
One-click install
npx skills add https://github.com/korwlik23/skills --skill code-review-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-refactor
Source: https://github.com/korwlik23/skills/tree/main/v1/code-review-refactor
Command: npx skills add https://github.com/korwlik23/skills --skill code-review-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you evaluate code quality and refactoring opportunities while minimizing the risk of breaking behavior, introducing security flaws, or degrading performance.

Core Features & Use Cases

  • Evidence-backed findings: Produces findings with severity, impact, and actionable fixes tied to the provided context.
  • Production-grade refactor discipline: Preserves existing behavior, keeps diffs readable, and breaks refactors into verifiable steps.
  • Comprehensive review coverage: Reviews correctness, security, performance, database/data integrity, API design, accessibility, and operational observability.
  • Refactor gating and prioritization: Separates must-fix risks from optional cleanup and classifies issues by severity.

Quick Start

Ask for a code review and refactor plan for the provided diff or snippet, requesting evidence-backed issues and smallest-step fixes.

Frequently Asked Questions about code-review-refactor

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

FAQPage Schema
How do I refactor legacy code safely for production without breaking existing behavior?

Safe refactoring for production requires preserving existing behavior, breaking changes into smallest verifiable steps, and keeping diffs readable to minimize regression risks before deployment.

What is the best way to structure code review findings for security and performance issues?

Code review findings should be structured by severity, location, impact, and evidence, separating must-fix security and performance risks from optional technical debt cleanup to prioritize actionable fixes.

Can I review API design and database integrity issues in the same code review pass?

Comprehensive code review evaluates API design, database integrity, accessibility, and operational observability simultaneously, assessing correctness, reliability, security, and performance in a single pass.

How do I prioritize technical debt cleanup when reviewing a pull request diff?

Prioritize technical debt cleanup by applying refactor gating to separate must-fix risks from optional cleanup, classify issues by severity, and require evidence-backed impact analysis before taking action.

Does evidence-backed code review work for reviewing architecture and security surfaces?

Evidence-backed code review works for architecture and security surfaces by tying findings to provided context with actionable fixes, evaluating reliability and data integrity under production-grade constraints.

When should I not use automated refactoring for technical debt?

Avoid automated refactoring when it risks altering existing behavior, as production-grade discipline requires preserving functionality unless explicitly requested and verifying changes before completion.