Source profileQuality 69/100

yun520-1/mark-heartflow-skill/skills/code-refactoring/SKILL.md

code-refactoring

Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.

Source repository stars
36
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/code-refactoring"
    Safe inspection promptEditorial

    Inspect the Agent Skill "code-refactoring" from https://github.com/yun520-1/mark-heartflow-skill/blob/20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c/skills/code-refactoring/SKILL.md at commit 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Safe Refactoring Process

      1. Ensure tests exist - Write tests if they don't 2. Make small changes - One refactoring at a time 3. Run tests after each change - Catch regressions immediately 4. Commit frequently - Easy to revert if something breaks 5. Review the diff - Make sure behavior hasn't changed

      Ensure tests exist - Write tests if they don'tMake small changes - One refactoring at a timeRun tests after each change - Catch regressions immediately
    2. 02

      Refactoring Principles

      Before adding new features (make change easy, then make easy change)

      Before adding new features (make change easy, then make easy change)After getting tests passing (red-green-refactor)When you see code smells
    3. 03

      When to Refactor

      Before adding new features (make change easy, then make easy change)

      Before adding new features (make change easy, then make easy change)After getting tests passing (red-green-refactor)When you see code smells
    4. 04

      When NOT to Refactor

      Without tests covering the code

      Without tests covering the codeUnder tight deadlines with no safety netCode that will be replaced soon
    5. 05

      Common Code Smells

      Review the “Common Code Smells” section in the pinned source before continuing.

      Review and apply the “Common Code Smells” source section.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score69/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars36SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    yun520-1/mark-heartflow-skill
    Skill path
    skills/code-refactoring/SKILL.md
    Commit
    20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c
    License
    Not declared
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Code Refactoring

    Refactoring Principles

    When to Refactor

    • Before adding new features (make change easy, then make easy change)
    • After getting tests passing (red-green-refactor)
    • When you see code smells
    • During code review feedback

    When NOT to Refactor

    • Without tests covering the code
    • Under tight deadlines with no safety net
    • Code that will be replaced soon
    • When you don't understand what the code does

    Common Code Smells

    Long Methods

    // BEFORE: Method doing too much
    function processOrder(order: Order) {
      // 100 lines of validation, calculation, notification, logging...
    }
    
    // AFTER: Extract into focused methods
    function processOrder(order: Order) {
      validateOrder(order);
      const total = calculateTotal(order);
      saveOrder(order, total);
      notifyCustomer(order);
    }
    

    Deeply Nested Conditionals

    // BEFORE: Arrow code
    function getDiscount(user: User, order: Order) {
      if (user) {
        if (user.isPremium) {
          if (order.total > 100) {
            if (order.items.length > 5) {
              return 0.2;
            }
          }
        }
      }
      return 0;
    }
    
    // AFTER: Early returns (guard clauses)
    function getDiscount(user: User, order: Order) {
      if (!user) return 0;
      if (!user.isPremium) return 0;
      if (order.total <= 100) return 0;
      if (order.items.length <= 5) return 0;
      return 0.2;
    }
    

    Primitive Obsession

    // BEFORE: Primitives everywhere
    function createUser(name: string, email: string, phone: string) {
      if (!email.includes('@')) throw new Error('Invalid email');
      // more validation...
    }
    
    // AFTER: Value objects
    class Email {
      constructor(private value: string) {
        if (!value.includes('@')) throw new Error('Invalid email');
      }
      toString() { return this.value; }
    }
    
    function createUser(name: string, email: Email, phone: Phone) {
      // Email is already validated
    }
    

    Feature Envy

    // BEFORE: Method uses another object's data extensively
    function calculateShipping(order: Order) {
      const address = order.customer.address;
      const weight = order.items.reduce((sum, i) => sum + i.weight, 0);
      const distance = calculateDistance(address.zip);
      return weight * distance * 0.01;
    }
    
    // AFTER: Move method to where the data is
    class Order {
      calculateShipping() {
        return this.totalWeight * this.customer.shippingDistance * 0.01;
      }
    }
    

    Refactoring Techniques

    Extract Method

    // Identify a code block that does one thing
    // Move it to a new method with a descriptive name
    // Replace original code with method call
    
    function printReport(data: ReportData) {
      // Extract this block...
      const header = `Report: ${data.title}\nDate: ${data.date}\n${'='.repeat(40)}`;
      console.log(header);
    
      // ...into a method
      printHeader(data);
    }
    

    Replace Conditional with Polymorphism

    // BEFORE: Switch on type
    function getArea(shape: Shape) {
      switch (shape.type) {
        case 'circle': return Math.PI * shape.radius ** 2;
        case 'rectangle': return shape.width * shape.height;
        case 'triangle': return shape.base * shape.height / 2;
      }
    }
    
    // AFTER: Polymorphic classes
    interface Shape {
      getArea(): number;
    }
    
    class Circle implements Shape {
      constructor(private radius: number) {}
      getArea() { return Math.PI * this.radius ** 2; }
    }
    
    class Rectangle implements Shape {
      constructor(private width: number, private height: number) {}
      getArea() { return this.width * this.height; }
    }
    

    Introduce Parameter Object

    // BEFORE: Too many parameters
    function searchProducts(
      query: string,
      minPrice: number,
      maxPrice: number,
      category: string,
      inStock: boolean,
      sortBy: string,
      sortOrder: string
    ) { ... }
    
    // AFTER: Parameter object
    interface SearchParams {
      query: string;
      priceRange: { min: number; max: number };
      category?: string;
      inStock?: boolean;
      sort?: { by: string; order: 'asc' | 'desc' };
    }
    
    function searchProducts(params: SearchParams) { ... }
    

    Replace Magic Numbers with Constants

    // BEFORE
    if (user.age >= 18 && order.total >= 50) {
      applyDiscount(order, 0.1);
    }
    
    // AFTER
    const MINIMUM_AGE = 18;
    const DISCOUNT_THRESHOLD = 50;
    const STANDARD_DISCOUNT = 0.1;
    
    if (user.age >= MINIMUM_AGE && order.total >= DISCOUNT_THRESHOLD) {
      applyDiscount(order, STANDARD_DISCOUNT);
    }
    

    Safe Refactoring Process

    1. Ensure tests exist - Write tests if they don't
    2. Make small changes - One refactoring at a time
    3. Run tests after each change - Catch regressions immediately
    4. Commit frequently - Easy to revert if something breaks
    5. Review the diff - Make sure behavior hasn't changed

    Refactoring Checklist

    • Tests pass before starting
    • Each change is small and focused
    • Tests pass after each change
    • No behavior changes (only structure)
    • Code is more readable than before
    • Commit message explains the refactoring

    Alternatives

    Compare before choosing