refactor-pass

Remove dead code and simplify logic while preserving build and test behavior.

102|4|Updated Apr 15, 2009
One-click install
npx skills add https://github.com/mikker/dotfiles --skill refactor-pass-mikker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-pass
Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/refactor-pass
Command: npx skills add https://github.com/mikker/dotfiles --skill refactor-pass-mikker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor passes address code complexity after changes by identifying simplifications, removing dead code, reducing parameters, and straightening logic flows to improve readability and maintainability.

Core Features & Use Cases

  • Identify dead code and dead paths to reduce unused logic.
  • Straighten control flows and remove unnecessary parameters.
  • Propose optional abstractions only when they clearly improve clarity and maintainability.

Quick Start

Review the latest changes and propose targeted refactors that simplify logic, remove dead code, and minimize parameters while ensuring behavior remains unchanged and tests pass.

Frequently Asked Questions about refactor-pass

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

FAQPage Schema
How do I simplify code and remove dead paths after recent changes?

A refactor pass identifies dead code and unnecessary parameters after recent changes, straightening logic flows to improve readability and maintainability while ensuring behavior remains unchanged.

What is the best way to reduce code complexity without breaking existing tests?

The best way to reduce code complexity without breaking tests is applying targeted refactors that straighten logic and remove dead code, then running the build and test suite to verify functionality is preserved and regressions are prevented.

When do I need a refactor pass for code maintenance?

You need a refactor pass when recent code changes introduce complexity, unused logic, or unnecessary parameters that degrade readability and require simplification while preserving behavior.

Can I propose optional abstractions to improve clarity during a code cleanup?

Yes, optional abstractions are proposed during code cleanup only when they clearly improve clarity and maintainability, ensuring the refactor pass preserves behavior across builds and tests.

Does refactoring code to minimize parameters risk breaking my build?

Refactoring to minimize parameters does not risk breaking the build when the process runs the build and test suite to verify behavior preservation and prevent regressions.