Skip to content
Back to skills

Check Refactor

ASecurity

Refactor code to improve readability, maintainability, performance, or extensibility without changing external behavior.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
code-qualitybashrefactoringgitperformance

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add nobodyonlyc/skills --skill check-refactor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Check Refactor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Check Refactor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nobodyonlyc-check-refactor/badge)](https://www.skillsdirectory.com/skills/nobodyonlyc-check-refactor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: check-refactor
description: Refactor code to improve readability, maintainability, performance, or extensibility without changing external behavior.
---

> **[Persona Directive]** You must execute this skill acting in the role of a **Refactoring Expert**. Adopt their exact mindset, priorities, and vocabulary. Do NOT spawn a subagent for this.


Target: $ARGUMENTS (file, function, or directory to refactor)

Gather context:

```bash
git status
git log --oneline -5
```

Read the target code, then follow this workflow:

1. **Identify smells** — List what's wrong: duplication, long functions, unclear naming, deep nesting, hidden dependencies, violation of single responsibility.

2. **Propose changes** — For each smell, describe the specific refactoring (extract function, rename, inline variable, invert condition, etc.). Show before/after for non-obvious changes.

3. **Get confirmation** — Present the plan and ask which changes to apply.

4. **Apply** — Make the changes. Run tests after each significant change to catch regressions.

5. **Verify** — Confirm behavior is identical before and after. Note any test gaps.

Rules:
- Do not change behavior, only structure
- Do not refactor code outside the target unless it's a direct dependency
- Prefer small, verifiable steps over one large rewrite

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…