Run any Skill in Manus with one click

refactor

Stars28

Forks2

UpdatedMay 17, 2026 at 17:54

Refactor existing code without changing behavior. Use when the user wants to improve readability, modularity, performance, type safety, or reduce duplication.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hawkyre

hawkyre/hawk-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	refactor
description	Refactor existing code without changing behavior. Use when the user wants to improve readability, modularity, performance, type safety, or reduce duplication.

Refactor Code

Process

Confirm the constraint (ask if not provided):
- Invariant: what must NOT change (behavior, API, tests passing)
- Dimension (pick ONE):
  - Readability (clearer naming, simpler control flow)
  - Modularity (break apart, extract, separate concerns)
  - Performance (reduce allocations, optimize hot paths)
  - Type safety (tighten types, eliminate any, add guards)
  - Deduplication (consolidate repeated patterns)
- Context: why this refactor, what pain it solves
Always pick ONE dimension. Multi-axis refactors produce unreadable diffs and are impossible to review.
Load context:
- Read relevant standards from .agents/standards/
- Read relevant common-mistakes from .agents/common-mistakes/
Outline the plan:
- Specific transformations to apply
- Order (each step leaves the check command passing)
- What the code will look like after (brief description, not full code)
- Risks or tricky parts
Execute incrementally: One step at a time. Confirm tests pass between steps. If something breaks, roll back one step, not the whole refactor.
Verify the invariant:
- Run the project's check command
- Diff the public API/interface — confirm nothing changed externally
- List any behavioral differences (there should be zero)

Rules

ALWAYS constrain to ONE dimension. Multi-axis refactors produce unreadable diffs.
Each step must leave tests passing
A refactor diff should be "boring" — moves, renames, restructures. No logic changes.
If you discover a bug during refactoring, note it for a separate fix PR. Never mix refactoring and bug fixes.
Check .agents/common-mistakes/ for relevant patterns before and after
Big-output discipline. Heavy command output (project check, full git diff, repo-wide search, long log, large fetch) goes to /tmp/hawk-<skill>-<step>.log, then rg -n '<pattern>' /tmp/hawk-<skill>-<step>.log | head -50 extracts what you need. Read the file only with offset/limit. See README → Big-output discipline.

More from this repository

same repository

plan-large

hawkyre/hawk-skills

Plan a multi-PR feature, migration, or architectural change before writing code. Writes a `.plans/<slug>/` directory of HTML documents (with inline UI mockups and a review-tracking layer) — a 1-page `overview.html` for human review, a mandatory `data-model.html` that locks the schema before anything else, a terse `plan.html` of dependency-ordered increments, an ADR-style `decisions.html`, and a `verification.html` acceptance script. Use whenever the user says "plan this feature", "scope out the migration", "/plan-large", "architect this rollout", "I need a plan covering schema and API", "design this across multiple PRs", or "break this work up". Also use whenever the work touches a database migration, even if it's only two PRs — schema-first is the gate. Runs a blind self-review subagent before presenting. Do NOT use for single-PR changes — bail to `plan-small` at Step 0. Do NOT use to start implementing — that's `/implement-plan` after the plan is approved.

2026-06-2828

plan-small

hawkyre/hawk-skills

Plan a single-PR change end-to-end before writing code. Writes a terse `.plans/<slug>/plan.html` (HTML, with inline UI mockups where a screen changes, rendered through the shared design system) covering files to touch, data-model changes, edge cases, verification, and decisions/assumptions sourced to code or user. Use whenever the user says "plan this", "scope this out", "write up a plan for X", "/plan-small", "let's plan the new flag", or "plan before we start". Also use whenever the user describes a small feature without explicitly asking to plan — propose a plan before coding. Asks only what code can't answer (in-repo PRDs count), surfaces planned assumptions alongside questions, then runs a blind self-review subagent before presenting. Do NOT use for multi-PR work, schema migrations beyond adding a nullable column, or sequenced increments — bail to `plan-large` at Step 0. Do NOT use to start implementing — that's `/implement-plan` after the plan is approved.

2026-06-2828

code-audit-hardcore

hawkyre/hawk-skills

Aggressive cleanup audit scoped to the user's specified changes plus tangibly-relevant surrounding code. Same blind audit-* specialists as code-audit, with a maximum-improvement posture — any code in the expanded review scope that can be cleaner WILL be made cleaner. Small fixes applied inline; big fixes (>5 files, schema, public API, redesigns) routed through `/plan-small` or `/plan-large`. Plan-overrides — when the audit reveals the original plan was wrong — route through `/plan-large` by default. Always improve over preserve.

2026-06-2828

implement-plan-audited

hawkyre/hawk-skills

Execute a plan increment-by-increment with the audit-* specialists running independently at strategic checkpoints. Use whenever the user says "implement the plan with audits", "audited implementation", "run with audits", "implement with cleanup checkpoints", "audit as you go", or invokes /implement-plan-audited. Inherits the full per-increment verification loop from `implement-plan` (done-criteria evidence, layered retry ladder, file-divergence check, outcome records) and adds checkpoint annotation, blind parallel audits, audit-fix verification (each FIX closes its own loop), plan-override propagation, and BEHAVIOR_CHANGE.md artifacts. Two modes — `manual` stops between increments for user review; `auto` applies audit fixes and proceeds without interruption, designed for hours of unattended execution. Specialists are blind to the plan and the goal. Do NOT use for unaudited plan execution — use `implement-plan`. Do NOT use for one-shot audits of existing code — use `code-audit`. Do NOT use for planning or repl

2026-06-2828

implement-plan

hawkyre/hawk-skills

Execute an approved plan increment-by-increment with deterministic verification at each step. Use whenever the user says "implement the plan", "run the plan", "execute the plan", "work through the increments", "do the plan", or invokes /implement-plan. Done-criteria are checked against evidence on disk, not asserted from memory; failures escalate through a layered ladder rather than repeated identical attempts; existing code gets behavior-preservation tests before modification; file divergence (touched vs declared) is reconciled before each commit; structured outcome records land in the plan file. Designed for fresh sessions with no prior context. Do NOT use for planning itself — use `plan-small` or `plan-large`. Do NOT use for unplanned coding without a plan file — use `coding-process`. Do NOT use when the user wants audits in the loop — use `implement-plan-audited`.

2026-06-2828

review-plan

hawkyre/hawk-skills

Stress-test a plan file before committing to implementation. Catches architectural mistakes, convention violations, and missing dependencies while changes are still cheap. Invoked directly, not routed from coding-process.

2026-06-2828

Refactor Code

Process

Confirm the constraint (ask if not provided):

Invariant: what must NOT change (behavior, API, tests passing)
Dimension (pick ONE):
- Readability (clearer naming, simpler control flow)
- Modularity (break apart, extract, separate concerns)
- Performance (reduce allocations, optimize hot paths)
- Type safety (tighten types, eliminate any, add guards)
- Deduplication (consolidate repeated patterns)
Context: why this refactor, what pain it solves

Always pick ONE dimension. Multi-axis refactors produce unreadable diffs and are impossible to review.

Load context:

Read relevant standards from .agents/standards/
Read relevant common-mistakes from .agents/common-mistakes/

Outline the plan:

Specific transformations to apply
Order (each step leaves the check command passing)
What the code will look like after (brief description, not full code)
Risks or tricky parts

Execute incrementally: One step at a time. Confirm tests pass between steps. If something breaks, roll back one step, not the whole refactor.

Verify the invariant:

Run the project's check command
Diff the public API/interface — confirm nothing changed externally
List any behavioral differences (there should be zero)

Rules

ALWAYS constrain to ONE dimension. Multi-axis refactors produce unreadable diffs.

Each step must leave tests passing

A refactor diff should be "boring" — moves, renames, restructures. No logic changes.

If you discover a bug during refactoring, note it for a separate fix PR. Never mix refactoring and bug fixes.

Check .agents/common-mistakes/ for relevant patterns before and after

Big-output discipline. Heavy command output (project check, full git diff, repo-wide search, long log, large fetch) goes to /tmp/hawk-<skill>-<step>.log, then rg -n '<pattern>' /tmp/hawk-<skill>-<step>.log | head -50 extracts what you need. Read the file only with offset/limit. See README → Big-output discipline.