refactoring SKILL.md skillA
refactoring from brunob54/superpowers-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add brunob54/superpowers-orchestrator/refactoring@git:20260415.0a78a70Pins git:20260415.0a78a70 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- brunob54/superpowers-orchestrator
- Path
skills/refactoring/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260415.0a78a70, committed Apr 15, 2026
- Size
- 7,305 bytes
- Repository stars
- 3
- License
- MIT
MUST USE when restructuring existing code without changing behavior: extracting functions/modules, inlining, simplifying, decoupling, reorganizing files, renaming across the codebase, or cleaning up code structure. Enforces behavior-locking tests before any structural change and incremental verification after each move. Distinct from brainstorming (which designs new behavior) and bug fixing (which changes behavior). Triggers on: "refactor", "restructure", "reorganize", "clean up this code…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Refactoring Change structure without changing behavior. Prove it at every step. ## Why This Exists Refactoring feels safe — "I'm just moving things around." That's exactly why it's dangerous. Without a behavior lock, structural changes silently break contracts, reorder side effects, or drop edge cases. This skill enforces the discipline that makes refactoring actually safe. ## Phase 1: Behavior Lock Before touching any structure, lock the current behavior with tests. 1. **Run the existing test suite.** Detect the project's test runner (check `package.json` scripts, `Makefile`, `pytest.ini`, `Cargo.toml`, etc.) and run it. Every test must pass. If tests fail before you start, you're debugging, not refactoring — switch to `systematic-debugging`. 2. **Identify the refactoring surface** — which functions, modules, or files will be structurally changed. 3. **Audit test coverage on that surface.** For each function/module in scope: - Is there a test that exercises its public API or observable behavior? - If yes: verify it passes. That test is now your behavior lock. …
Read the whole file at its exact version.
How to install
mdr add brunob54/superpowers-orchestrator/refactoring@sha256:3e68659bf53d0336The line at the top of this page pins the label git:20260415.0a78a70, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2rgt4pst2vhnr4dr)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 15, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7305 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
brunob54/superpowers-orchestrator · 3 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2rgt4pst2vhnr4dr GET https://markdownregistry.com/api/v1/resolve?ref=brunob54/superpowers-orchestrator/refactoring GET https://markdownregistry.com/api/v1/blob/3e68659bf53d03360f842066c1e2e33bcdd918f23c2f27f11ffe30baf920f50c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from brunob54/superpowers-orchestrator
Every file in brunob54/superpowers-orchestrator