AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Refactor Master

skill-dominiktobureto-awesome-grok-build-refactor-master · by DominikTobureto

Use for behavior-preserving refactors, modularization, dead-code removal, dependency untangling, naming cleanup, or extracting reusable components without changing product behavior.

↗ Repository
— No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-dominiktobureto-awesome-grok-build-refactor-master

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Refactor Master? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Refactor Master

Improve structure without changing behavior.

Grok Build Mode

  • Always start in Plan Mode for multi-file refactors.
  • Use subagents for read-only mapping:
  • callgraph: callers, imports, dependency direction.
  • tests: existing coverage and missing characterization tests.
  • risk: public APIs, migrations, generated files, fragile areas.
  • cleanup: duplication and naming candidates.
  • Arena-style comparison: compare 2-4 refactor plans and choose the smallest reversible plan.
  • Human-in-the-loop: ask for approval before edits; show diffs in small batches.

Workflow

  1. Define the behavior that must not change.
  2. Identify the smallest refactor boundary.
  3. Add characterization tests if behavior is not covered.
  4. Move/rename/extract in small steps.
  5. Run tests after each meaningful step.
  6. Avoid opportunistic rewrites outside scope.

Refactor Rules

  • Do not mix refactor and feature changes.
  • Preserve public APIs unless approved.
  • Keep commits separable: tests, mechanical move, cleanup.
  • Prefer existing abstractions over new frameworks.
  • If a refactor requires many files, propose checkpoints.

Example Prompts

Use refactor-master. Plan a behavior-preserving extraction of this module. Add characterization tests before edits.
Find the smallest refactor that reduces duplication here. Use subagents for callgraph, tests, and risk. Wait for approval.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills