style

Normalizes whitespace, wrapping, quoting, and ordering in code and text without changing behavior.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill style-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: style
Source: https://github.com/kieranpotts/skills/tree/main/skills/style
Command: npx skills add https://github.com/kieranpotts/skills --skill style-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Formatting inconsistencies pollute diffs, hide real logic changes, and cause CI failures. This Skill applies presentation-only changes — whitespace, indentation, line wrapping, quotes, import ordering — using the project's own formatter, so style fixes stay out of behavior commits and remain reviewable. ## Core Features & Use Cases - Formatter discovery and execution: Finds the project's configured formatter via config files, task runner scripts, or commit hooks, and runs it as configured rather than hand-editing. - Scope control: Defaults to the narrowest scope covering the target files, keeping diffs reviewable and avoiding repo-wide noise. - Behavior verification: Runs the project's test suite after formatting and checks git diff -w to prove the change is semantically empty. - Use Case: After finishing a feature, run this Skill to format the touched files as a separate style-typed commit, so the logic diff stays clean and reviewers see two readable changes instead of one noisy one. ## Quick Start Format the files I just changed in the working tree and file the result as a single style commit.

Frequently Asked Questions about style

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

FAQPage Schema
How do I format code without changing its behavior?▼

Run the project's configured formatter at the narrowest scope covering your target files, then run the test suite to confirm behavior is unchanged. For whitespace-only changes, verify with git diff -w that the diff is empty.

How to keep formatting changes out of feature commits?▼

File formatting as a separate style-typed commit after the behavior change is complete. Mixed commits hide substantive logic inside formatting noise and make history hard to review.

Can I reformat code when the project has no formatter configured?▼

Yes, fall back to the conventions the surrounding files already follow, but record a follow-up maintenance task to add a formatter config, wire it into a commit hook, and add a CI check.

Does reformatting work safely with Python or YAML files?▼

Significant-whitespace languages like Python, YAML, and Make require extra care because re-indentation can change meaning. Always run the full test suite after formatting and parse any reformatted configuration files.

When should I not use a formatting pass?▼

Do not use it for renames, function extractions, parameter reordering, or prose wording edits — those are refactors or proofreading. Also never reformat generated, transpiled, or vendored files, since the generator owns their format.