skills.rest
Tiepbm
TiepbmCOMMUNITY
Explore all skills by this author →
GitHub

code-review-and-refactoring

Identify maintainability and risk issues in codebases and plan incremental refactors.

Updated Apr 25, 2026
Search Tags:#testing#architecture#refactoring#maintainability#code-review#technical-debt
One-click install
npx skills add https://github.com/Tiepbm/software-engineering-agent --skill code-review-and-refactoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-refactoring
Source: https://github.com/Tiepbm/software-engineering-agent/tree/main/skills/code-review-and-refactoring
Command: npx skills add https://github.com/Tiepbm/software-engineering-agent --skill code-review-and-refactoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineering teams identify and prioritize maintainability and risk issues in codebases, guiding safe, incremental refactoring to protect delivery, behavior, and production stability.

Core Features & Use Cases

  • Assess correctness, readability, coupling, cohesion, abstraction quality, error handling, data access, security, performance, and test coverage.
  • Identify hidden complexity, leaky boundaries, and risky dependencies; propose safe refactoring sequences that minimize blast radius and preserve public contracts.
  • Escalate to specialized skills (e.g., security-review, api-design, database-reliability) when needed to protect regulatory and operational requirements.

Quick Start

Review a PR or legacy module and propose a safe, incremental refactor plan with tests and rollback awareness.

Frequently Asked Questions about code-review-and-refactoring

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

FAQPage Schema
How do I plan a safe refactoring strategy for legacy modules?▼

Plan legacy module refactoring by applying a structured review checklist to identify maintainability issues, prioritize risky changes, and sequence incremental refactors with tests and explicit rollback paths.

What is the best way to review a pull request for technical debt and maintainability?▼

Review pull request technical debt by assessing correctness, coupling, cohesion, and test coverage, then proposing a safe, incremental refactor plan that minimizes blast radius and preserves public contracts.

How do I reduce risk when refactoring complex background jobs and data access layers?▼

Reduce refactoring risk in background jobs and data access layers by identifying hidden complexity and leaky boundaries, then planning incremental changes that protect production stability and preserve behavior.

Can I escalate code review findings to specialized security and database reliability checks?▼

Yes, code review findings can escalate to specialized reviews for security and database reliability, ensuring that refactoring plans protect regulatory and operational requirements across complex API and data access boundaries.

When should I avoid a big bang rewrite and use staged refactors instead?▼

Avoid big bang rewrites when dealing with risky dependencies and complex rework; use staged refactors to enforce explicit boundaries, minimize blast radius, and maintain delivery stability.

Related Skills

Explore More Software Engineering Skills→
Pabloprogramador23Pabloprogramador23

reversa-archaeologist

Analyze legacy codebases module by module to extract algorithms, control flows, and data structures.

Community
Advanced
z3z1maz3z1ma
21

subsystem-removal-checklist

Guide safe subsystem removal with public surface mapping and validation gates.

Community
Advanced
nekorush14nekorush14
4

rails-security

Implement security best practices for Rails authentication, authorization, and API protection.

Community
Intermediate
dhruvinrsonidhruvinrsoni

cleanup

Remove dead code, enforce formatting standards, and rename identifiers.

Community
Advanced