stylistic-refactor-creator

Generate a project-specific SKILL.md, style reference files, and a prioritized refactoring plan.

7|4|Updated Mar 2, 2026

Search Tags:#automation #refactor #skill-creation #code-style #stylistic #developer-preferences

Ready to run

npx skills add https://github.com/nklisch/skills --skill stylistic-refactor-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stylistic-refactor-creator
Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/stylistic-refactor-creator
Command: npx skills add https://github.com/nklisch/skills --skill stylistic-refactor-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many projects lack a dedicated stylistic‑refactor skill, causing inconsistent code style decisions and missed refactoring opportunities. This skill creates or updates a custom stylistic‑refactor skill that captures the team's preferred coding conventions.

Core Features & Use Cases

Discovery: Scans the repository to identify existing style patterns.
Research: Retrieves stack‑specific style guides and best‑practice recommendations.
Interview: Converses with the user to finalize preferred stylistic rules.
Generation: Produces a new SKILL.md, reference markdown files for each style, and a prioritized refactoring plan.

Quick Start

Run the stylistic‑refactor‑creator skill and answer the prompts to define your project's coding style preferences.

Frequently Asked Questions about stylistic-refactor-creator

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

FAQPage Schema

How do I create a project-specific coding style guide beyond linting?▼

You can create a coding style guide by running this skill to scan your repository for existing patterns, research stack-specific best practices, and interview your team. It generates a SKILL.md, reference files, and a prioritized refactoring plan.

What is a stylistic refactor and when do I need it?▼

A stylistic refactor enforces unified team coding conventions beyond standard linting. You need it when your codebase suffers from inconsistent style decisions and missed refactoring opportunities, requiring a dedicated skill to capture and enforce preferred guidelines.

How do I automate capturing developer preferences for code style?▼

You automate capturing developer preferences by conversing with this skill through an interview process. It finalizes your preferred stylistic rules based on repository exploration and stack research, then outputs a concise SKILL.md and reference files.

Can I generate a refactoring plan for my codebase's coding style?▼

Yes, you can generate a prioritized refactoring plan for your codebase's coding style. The skill produces this plan alongside a new SKILL.md and reference markdown files for each style, targeting your project's specific language and frameworks.

Does this stylistic refactor skill work with any programming language?▼

Yes, the skill applies to codebases of any language and framework. It researches stack-specific style guides and best-practice recommendations during its discovery phase to tailor the generated stylistic guidelines to your environment.

What is the difference between this and standard linting rules?▼

Unlike standard linting, this skill captures and enforces team coding style preferences that go beyond automated linting checks. It targets stylistic guidelines through repository exploration and user interviews to produce a custom refactoring plan.