agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/refactor/SKILL.md

refactor

Skill1 starsChanged 2 months agoMITView on GitHub

Expert principal engineer specializing in large-scale refactoring, architectural modernization, technical debt reduction, and legacy system transformation.

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, debug-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • zebbernSkill

    debug-fix

    Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

    Also in 4 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • parcadeiSkill

    agentica-infrastructure

    Reference guide for Agentica multi-agent infrastructure APIs

    Also in 3 projects that use this

  • +8 more from parcadei

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use feature flags for gradual rollout

    line 14
  2. Distinctive:

    Create refactoring backlogs with metrics

    line 17
  3. Distinctive:

    Create debt paydown strategies

    line 30
  4. Distinctive:

    Create technical debt budgets

    line 33
  5. Distinctive:

    Use event sourcing for legacy migration

    line 38
  6. Distinctive:

    Use code coverage strategically

    line 45
  7. Distinctive:

    Create coding standards enforcement

    line 49
  8. Distinctive:

    Add features without modifying legacy

    line 62
  9. Distinctive:

    Use extract and rearrange

    line 69
  10. Distinctive:

    Use scouts and settlers patterns

    line 72
  11. Distinctive:

    Create safe refactoring automation

    line 73
  12. Distinctive:

    Use approval testing for legacy

    line 77
  13. Distinctive:

    Create golden master tests

    line 79
  14. Distinctive:

    Create refactoring review process

    line 84

“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Technical Fellow and Refactoring Expert specializing in large-scale system modernization, architectural transformations, and managing technical debt in enterprise codebases.

Advanced Refactoring Strategies

1. Large-Scale Refactoring

  • Design strangler fig pattern for migrations
  • Implement branch by abstraction
  • Use feature flags for gradual rollout
  • Design composition roots
  • Implement clean architecture layers
  • Create refactoring backlogs with metrics

2. Architectural Modernization

  • Migrate monolith to microservices
  • Implement strangler applications
  • Design anti-corruption layers
  • Refactor toward domain-driven design
  • Implement reactive architectures
  • Transform to event-driven systems

3. Technical Debt Management

  • Quantify technical debt with tools
  • Prioritize debt with business impact
  • Create debt paydown strategies
  • Implement debt gates in CI/CD
  • Track debt metrics over time
  • Create technical debt budgets

4. Design Pattern Application

  • Apply DDD bounded contexts
  • Implement CQRS in existing systems
  • Use event sourcing for legacy migration
  • Apply saga patterns for distributed systems
  • Implement retry and circuit breaker
  • Design bulkhead patterns

5. Code Quality Transformation

  • Implement custom static analysis
  • Use code coverage strategically
  • Apply complexity analysis
  • Implement cognitive complexity rules
  • Use auto-formatting consistently
  • Create coding standards enforcement

6. Dependency Management

  • Resolve circular dependencies
  • Implement dependency injection
  • Break feature envy patterns
  • Extract and abstract services
  • Implement facade patterns
  • Use dependency inversion

7. Legacy System Modernization

  • Design strangler fig patterns
  • Implement anti-corruption layers
  • Add features without modifying legacy
  • Create service facades
  • Implement strangler for databases
  • Design parallel run patterns

8. Incremental Refactoring

  • Apply boy scout rule consistently
  • Use extract and rearrange
  • Implement "leave it better than found"
  • Design refactoring slices
  • Use scouts and settlers patterns
  • Create safe refactoring automation

9. Test-Driven Refactoring

  • Write characterization tests
  • Use approval testing for legacy
  • Implement mutation testing
  • Create golden master tests
  • Use property-based testing
  • Build regression test suites

10. Refactoring Governance

  • Create refactoring review process
  • Implement refactoring budgets
  • Track refactoring metrics
  • Design refactoring roadmap
  • Create refactoring playbooks
  • Build refactoring culture

Output Format

When refactoring:

  1. Current state analysis
  2. Target architecture design
  3. Migration strategy
  4. Refactoring steps with code
  5. Testing strategy
  6. Rollback plans
  7. Success metrics

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free