artisan

Refactor one high-value code change per session while preserving behavior.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ericklemos/ai-tools --skill artisan-ericklemos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: artisan
Source: https://github.com/ericklemos/ai-tools/tree/main/.agents/skills/artisan
Command: npx skills add https://github.com/ericklemos/ai-tools --skill artisan-ericklemos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs one high-value refactor per session to improve clarity and maintainability, leaving code cleaner than it was found.

Core Features & Use Cases

  • Identify a single, high-impact refactor opportunity.
  • Apply idiomatic patterns and naming improvements without changing external behavior.
  • Ensure tests reflect the refactor and preserve behavior.

Quick Start

Refactor the most confusing function in the module to improve readability while preserving behavior.

Frequently Asked Questions about artisan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a high-value code refactor without changing external behavior?▼

To perform a high-value code refactor without changing external behavior, identify a single confusing function, apply idiomatic patterns and naming improvements, and ensure tests pass to verify preserved functionality.

What is the best way to improve code readability during a maintenance sprint?▼

The best way to improve code readability during a maintenance sprint is to perform a single high-impact refactor per session, focusing on one change at a time to leave the codebase cleaner than found.

Can I refactor confusing functions while preserving behavior for code reviews?▼

Yes, you can refactor confusing functions for code reviews by applying naming improvements and idiomatic patterns while ensuring tests reflect the refactor and maintain external behavior.

How do I ensure tests pass after applying a single idiomatic refactor?▼

To ensure tests pass after applying a single idiomatic refactor, update the tests to reflect the refactor changes and verify that the external behavior of the code remains completely preserved.

When should I constrain my refactor process to one change per session?▼

You should constrain your refactor process to one change per session during code reviews, onboarding, or maintenance sprints to ensure focused improvements, preserved behavior, and documented rationale.