quick-refactor

Cleans up code changes in an open PR before review without altering behavior.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/aitit-inc/leadace --skill quick-refactor-aitit-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-refactor
Source: https://github.com/aitit-inc/leadace/tree/main/.claude/skills/quick-refactor
Command: npx skills add https://github.com/aitit-inc/leadace --skill quick-refactor-aitit-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After opening a PR, code often contains leftover comments, dead code, and symptomatic patches that slow down review. This Skill performs a focused cleanup pass on the change before the Codex review, keeping behavior identical. ## Core Features & Use Cases - Scoped cleanup pass: Works only on the changed content (uncommitted changes by default, or a commit range/PR number via arguments), removing unnecessary comments, waste, and symptomatic guards. - LLM-facing text tightening: Shortens prompts, skill text, and tool descriptions without changing meaning. - Verification and reporting: Runs the project's checks (typecheck, tests, frontend checks) and reports what was removed, what was left out of scope, and any check failures. - Use Case: You just opened a PR for a feature branch and want a high-effort Opus subagent to strip redundant comments and simplify the diff before reviewers see it. ## Quick Start Ask Claude to run a quick refactor on the changes in the current PR before the Codex review.

Frequently Asked Questions about quick-refactor

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

FAQPage Schema
How do I clean up code changes before a PR review?

Run a quick refactor pass scoped to the diff of your open PR. It removes unnecessary comments, dead code, and symptomatic guards while keeping behavior identical, then runs the project's checks and reports the results.

What changes does a refactoring pass make to my code?

It deletes comments that restate the code, removes waste the change does not need, replaces one-off guards with general rules, and shortens prompts or tool descriptions. Content outside the change is left untouched and noted in the report.

Can I limit the refactor to specific files or a commit range?

Yes. Passing file names as arguments narrows the baseline to those files, while a commit range or PR number replaces the default baseline of uncommitted changes entirely.

Does the refactor commit or push changes automatically?

No. The skill explicitly does not commit, push, or merge. It only edits the working tree, runs verification checks such as typecheck and tests, and reports what was changed and why.

What happens if the verification checks fail after refactoring?

The skill runs the area's checks defined in the project configuration, such as npm run typecheck and npm test. On failure, it includes the check output verbatim in its report so you can diagnose the issue.