Menu

Individual skill

refactor-loop

Autonomous /goal loop that refactors a project on every axis without changing its behavior. Start it only when the user names refactor-loop.

plugins/reidemeister94/development-skills/skills/refactor-loop/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Refactor loop

Improve this project on every axis: structure, data model, queries, performance, readability, tests, and docs.
Behavior must stay identical: same outputs, side effects, contracts, and functional logs. Zero regressions. The only exception is a fix for a real bug.
The arguments of the request can set a focus, a branch, or extra limits.

Invoking this skill approves the work below within the [unattended-run limits](../../shared/unattended-runs.md).
Work on a new branch, `refactor/loop-YYYY-MM-DD`, unless the arguments name one. When data matters, use representative dev or staging data.
Keep every external contract: API schemas and fields, CLI output, event and file formats, shared database schemas, config names, and logs that alerts read. Internal names can change.

Fix real bugs and harmful side effects when the evidence proves them. Record each fix with before and after, and demonstrate the correction against the baseline.
When you are not sure it is a bug, record the question with your recommendation and continue independent work.

## Verification first