Skip to content
Skills Library
Programming · Review & audit

refactor

/refactor

Use to inspect a bounded area for code smells and discuss whether a behavior-preserving cleanup is worthwhile. Diagnosis only; implementation happens separately through simplify when the user asks to proceed.

Author
rjroy ↗
Repository
vibe-garden ↗
Licence
MIT
Last repository change
06.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use to inspect a bounded area for code smells and discuss whether a behavior-preserving cleanup is worthwhile. Diagnosis only; implementation happens separately through simplify when the user asks to proceed.

Original author description

Use to inspect a bounded area for code smells and discuss whether a behavior-preserving cleanup is worthwhile. Diagnosis only; implementation happens separately through simplify when the user asks to proceed.

How it works

  1. Scope and investigation
  2. Findings and user choice
Original SKILL.md headings · 46 lines, 371 words
SKILL.md preview
---
name: refactor
description: Use to inspect a bounded area for code smells and discuss whether a behavior-preserving cleanup is worthwhile. Diagnosis only; implementation happens separately through simplify when the user asks to proceed.
---

# Refactor

Begin with read-only diagnosis. The goal is to help the user decide whether a
concrete refactoring is worth doing, not to produce a checklist or change code.

## Scope and investigation

Establish the area or upcoming change from the user's request and conversation.
If it is unclear, ask one bounded question before exploring. Do not infer a
large scope from Git state or sweep the repository by default.

Inspect the relevant implementation, tests, callers, and consumers to understand
what the code does and where maintenance friction occurs. Use code search,
exploration, or a suitable review agent in proportion to the scope. Treat old
plans, designs, and other work artifacts as context only; current user intent
governs.

Use Fowler's code-smell vocabulary as a set of diagnostic cues, not a required
catalog to complete. For example, duplication can cause fixes to diverge;
shotgun surgery can make one change touch many places; speculative generality
can impose abstraction costs without a demonstrated need; lazy elements,
middle men, data clumps, and primitive obsession can obscure responsibilities
or concepts. Long methods, feature envy, message chains, global or mutable
state, and other familiar smells may also be relevant. A loop, switch, data
class, comment, or simple name is not inherently a defect. Consider conflicting
cues and the actual design context rather than treating any pattern as proof.

## Findings and user choice

Report only findings supported by concrete file and code evidence. Explain the
actual maintenance or future-change cost, then offer a bounded,
behavior-preserving correction option. Ordinary naming or formatting concerns
are not findings unless they cause meaningful cost. No finding is a valid
result; do not invent work to fill a quota.

Present findings to the user and let them choose whether, and which, to address.
Do not edit files, apply fixes, or begin implementation during this diagnosis.
If the user asks to proceed, hand `/simplify` only the selected findings and
compact scope: affected files/surface, evidence, behavior to preserve, and any
explicitly accepted change. Do not create a spec, matrix, or approval document.

If investigation shows that behavior must change, or behavior is unknown in a
way that affects the proposed correction, pause and discuss that separately;
never bundle it quietly into a behavior-preserving cleanup.

Versions

RepositoryScoreLicence
This page · rjroy/vibe-garden95MIT
froglet-studio/cosmic-shore100MIT
mgiovani/cc-arsenal100MIT
jongio/skills100MIT
boshu2/agentops100Apache-2.0
y-miyazaki/terraform-aws-base100Apache-2.0
mickeyyaya/evolve-loop100Apache-2.0
j0hanz/j0hanz-marketplace100MIT
kriscard/kriscard-claude-plugins100MIT

Database snapshot: 13.11.2026 · package version ce57cea5ed15 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-simplification
    Find dead code, duplication, overengineering, invented APIs, weak tests; report safe reductions, no edits. Use for "simplify this" or a refactor that lost behavior.
  • 90simplifier
    Expertise in simplifying and refining code for clarity, consistency, and maintainability while preserving all functionality. Use when the user asks to "simplify code", "refactor for clarity", or "clean up this file".
  • 90code-review
    Review the changes since a fixed point (commit, branch, tag, or merge-base) for the quality of the implementation itself: correctness, security, performance, and this repo's documented coding standards plus a baseline of code smells. Runs the axes as parallel sub-agents and…
  • 90refactoring-catalog
    Use when improving the structure of existing code without changing behavior — identifying code smells and applying the right named refactoring safely. Covers the discipline of behavior-preserving change; see CATALOG.md for the smell→fix reference.
  • 90dev-refactor-plan
    Use when the user asks for a behavior-preserving refactor plan before implementation. Do not trigger when the user already requested a clear, scoped refactor to be implemented directly.
  • 100workflow-refactor
    Scoped, behavior-preserving refactor: map dependencies, change structure, run affected tests. Use when "refactor this", "reduce duplication", or "improve readability". Dead code → plan-dead-code. Repo-wide smells → audit-code-quality.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.