New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Refactoring

by macalbert in macalbert/envilder

Code-smell detection and safe incremental refactoring patterns.

MITAuto-check passedDevelopment

Install Code Refactoring

skills CLI
$ npx skills add macalbert/envilder --skill code-refactoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install macalbert/envilder code-refactoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/code-refactoring .claude/skills/code-refactoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-refactoring
GitHub stars
138
Token cost
~1.1k tokens
SKILL.md length
493 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Code-smell detection and safe incremental refactoring patterns.

  • Works in 5 steps: Read target files, callers, verification… → Identify only concrete smells with… → Apply the deletion test to shallow… → …
  • Implementing a PUREREFACTOR contract
  • SKILL.md covers When to Use, Preconditions, Smell Catalog and Review Method, plus 4 more sections
  • Calls dotnet, pnpm and make

What it does

Code Refactoring is an agent skill from macalbert/envilder. Code-smell detection and safe incremental refactoring patterns. Use when reviewing or implementing a PUREREFACTOR contract, reducing technical debt, or assessing structural findings. Covers SOLID principles and behavior-preserving execution.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

  • Implementing a PUREREFACTOR contract
  • Reducing technical debt
  • Assessing structural findings

Example prompts

  • “/code-refactoring”

Requirements

  • Python 3
  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read target files, callers, verification contract, and architecture rules.
  2. Identify only concrete smells with maintenance or correctness risk.
  3. Apply the deletion test to shallow modules: retain an abstraction when
  4. Report location, evidence, proposed structural outcome, and risk.
  5. Accept no changes required when the candidate is already clear and

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet
    • pnpm
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Refactoring loads about 1.1k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 493 words, ~1,062 tokens.

Download SKILL.mdSave it as .claude/skills/code-refactoring/SKILL.md (or your agent's skills folder).
name
code-refactoring
description
Code-smell detection and safe incremental refactoring patterns. Use when reviewing or implementing a PURE_REFACTOR contract, reducing technical debt, or assessing structural findings. Covers SOLID principles and behavior-preserving execution.

Code Refactoring

Detect concrete code smells and improve structure while preserving all observable behavior. common-verification-first governs intent, protected artifacts, and evidence.

When to Use

  • Implementing an approved PURE_REFACTOR.
  • Reviewing a candidate for justified structural findings.
  • Reducing technical debt within approved scope.
  • Reducing complexity flagged by CRAP evidence.

Preconditions

  • Establish an existing-suite baseline before solution edits.
  • Freeze and protect behavioral verification; do not rewrite it for the refactor.
  • State architecture constraints and the behavior that must remain unchanged.
  • Only @Implementer applies workflow changes. @Reviewer remains read-only and reports findings to the orchestrator.

Smell Catalog

SmellIndicator
Long methodExcessive branches, mixed levels, or multiple responsibilities
Large classMultiple independent reasons to change
Duplicated logicThe same decision or transformation exists in multiple places
Tight couplingHigh-level behavior depends directly on replaceable details
Mixed abstractionPolicy and low-level mechanics are interleaved
Architecture violationA dependency crosses a prohibited layer boundary
Feature envyBehavior primarily manipulates another owner's data
Shallow moduleInterface complexity approaches implementation complexity
Primitive obsessionDomain concepts lack meaningful types and invariants
Speculative generalityAbstraction exists without a current requirement

Review Method

  1. Read target files, callers, verification contract, and architecture rules.
  2. Identify only concrete smells with maintenance or correctness risk.
  3. Apply the deletion test to shallow modules: retain an abstraction when removing it concentrates complexity; inline it when removal merely shortens the call path.
  4. Report location, evidence, proposed structural outcome, and risk.
  5. Accept no changes required when the candidate is already clear and cohesive.
Show full SKILL.md (244 more words)Show less

Implementation Method

For each approved structural change:

  1. Make one coherent transformation.
  2. Keep protected verification artifacts unchanged.
  3. Run the targeted existing verification.
  4. Run the stack formatter and static or build checks in the appropriate mode.
  5. Continue only while behavior and architecture constraints remain protected.
  6. Run the broader relevant suite before completion.

If a behavioral test must change, stop. The task may be a behavior change, the test may be coupled to private structure, or the contract may be defective. Route that decision to the orchestrator instead of silently reclassifying it.

Stack Checks

StackTypical verificationFormatter
TypeScript core, Node.js SDK, websiteTargeted Vitest or build, type checkpnpm format
.NET SDKTargeted and broader dotnet test, builddotnet format
Python SDKTargeted and broader pytest, mypymake format-sdk-python

Constraints

  • Never change observable outputs, side effects, compatibility, or domain invariants.
  • Respect Domain -> Application -> Infrastructure dependency rules.
  • Do not add tests merely to raise coverage or satisfy a refactoring ritual.
  • If important behavior truly lacks evidence, report a separate verification need; do not expand the frozen refactor contract.
  • Do not force a modification after review; no findings is valid.

SOLID Reference

PrincipleCheck
Single ResponsibilityDoes this unit have one reason to change?
Open/ClosedCan required variation be added without unstable branching?
Liskov SubstitutionCan subtypes replace the abstraction without surprises?
Interface SegregationDo clients depend only on operations they need?
Dependency InversionDoes policy depend on abstractions rather than details?

© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/code-refactoring of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Code Refactoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Refactoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Refactoring this skillmacalbert/envilder138—~1.1kAutomated safety check: PassMIT
Guidelinesakash-network/node1.1k22 repos~577Automated safety check: PassMIT
Component Refactoringlangflow-ai/langflow156k—~3.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed

More from macalbert/envilder

All 30 skills in this repo

  • Code Review Perspectives

    macalbert/envilder

    Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

    138 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

  • Common Architecture Decisions

    macalbert/envilder

    Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Common Git

    macalbert/envilder

    Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

    138 GitHub stars~991 tokensUpdated 2 days ago
    Auto-check passed

  • Common Testing Conventions

    macalbert/envilder

    Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).

    138 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Doc Maintenance

    macalbert/envilder

    Workflow for maintaining changelogs, READMEs, and documentation files.

    138 GitHub stars~904 tokensUpdated 2 days ago
    Auto-check passed

  • Doc Sync

    macalbert/envilder

    Audit and synchronize documentation across website, READMEs, and docs/.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Code Refactoring

What does Code Refactoring do?

Code-smell detection and safe incremental refactoring patterns. Code Refactoring is an agent skill from macalbert/envilder. Code-smell detection and safe incremental refactoring patterns.

When should I use Code Refactoring?

Code Refactoring fits situations like: implementing a PUREREFACTOR contract; reducing technical debt; assessing structural findings.

How do I install Code Refactoring in Claude Code?

Run `npx skills add macalbert/envilder --skill code-refactoring -a claude-code`. Or copy the skill folder (.github/skills/code-refactoring in macalbert/envilder) into .claude/skills/code-refactoring in your project. Claude Code loads it when a task matches its description.

How do I install Code Refactoring in Codex?

Run `npx skills add macalbert/envilder --skill code-refactoring -a codex`. Or copy the skill folder (.github/skills/code-refactoring in macalbert/envilder) into .agents/skills/code-refactoring in your project. Codex loads it when a task matches its description.

Can I use Code Refactoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill code-refactoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-refactoring, .gemini/skills/code-refactoring, .github/skills/code-refactoring and .opencode/skills/code-refactoring in your project.

What does Code Refactoring need to run?

Going by SKILL.md and its folder, Code Refactoring needs the command-line tools its instructions call (dotnet, pnpm and make). Our summary lists: Python 3; Node.js.

Does Code Refactoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Refactoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Refactoring use?

Code Refactoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Refactoring use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Refactoring?

Skills that share tags, products or a category with Code Refactoring: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Refactoring?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.