agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/refactor-code/SKILL.md

refactor-code

Skill9 starsChanged 3 months agoMITView on GitHub

Refactor for clarity without behavior change

16 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-tests, create-pr and 1 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.
  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 3 projects that use this

  • +1 more from getsentry

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 5

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Add appropriate comments where needed

    line 24
  2. Distinctive:

    Follow SOLID principles and design patterns

    line 25
  3. Distinctive:

    Keep changes within the refactor target.

    line 43
  4. Distinctive:

    Do not commit, push, merge, or run production scripts without consent.

    line 44
  5. Distinctive:

    Do not print, log, or commit secrets or credentials encountered while refactoring.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 15 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

Overview

Refactor the selected code to improve its quality while maintaining the same functionality, providing the refactored code with explanations of the improvements made.

Steps

  1. Code Quality Improvements
    • Extract reusable functions or components
    • Eliminate code duplication
    • Improve variable and function naming
    • Simplify complex logic and reduce nesting
  2. Performance Optimizations
    • Identify and fix performance bottlenecks
    • Optimize algorithms and data structures
    • Reduce unnecessary computations
    • Improve memory usage
  3. Maintainability
    • Make the code more readable and self-documenting
    • Add appropriate comments where needed
    • Follow SOLID principles and design patterns
    • Improve error handling and edge case coverage

Refactor Code Checklist

  • Extracted reusable functions or components
  • Eliminated code duplication
  • Improved variable and function naming
  • Simplified complex logic and reduced nesting
  • Identified and fixed performance bottlenecks
  • Optimized algorithms and data structures
  • Made code more readable and self-documenting
  • Followed SOLID principles and design patterns
  • Improved error handling and edge case coverage

Guardrails

  • Preserve existing behavior; a refactor must not change observable output.
  • Keep changes within the refactor target; do not touch unrelated code.
  • Do not commit, push, merge, or run production scripts without consent; wait for an explicit request before any destructive git action.
  • Do not print, log, or commit secrets or credentials encountered while refactoring; flag any exposed secret instead.

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