Polaris: Skill for Claude Code

Targeted Code-Formatting and Auto-Fix Style Skill

Objective

Enforce strict syntactic consistency and layout rules strictly across files altered or introduced in the workspace OR by the active issue ticket, fixing auto-resolvable lint issues and aligning modified blocks with standard project coding guidelines.

Guardrail Constraints

• Isolation Principle: Only perform formatting actions on files touched in the workspace OR by the current ticket. Do not introduce refactors, delete unrelated feature modules, or modify logical variable assignments. Never run global repository-wide formatting commands inside an isolated workspace OR ticket lifecycle.
• Scope Extraction Invariant: Before running any style checks, you must explicitly identify the modified file paths using local version control records or active workspace diffs.
• Safety Invariant: If targeted lint fixes produce errors that cannot be solved automatically, do not attempt to guess manual overrides; log the file paths and error details clearly for the developer or next workflow block and report when completed.

---

Execution Steps

Execute these formatting and correction operations sequentially to standardize your targeted code alterations:

Step 1: Identify Targeted Changes

Locate and isolate the precise file paths modified or created in the workspace OR as part of the current ticket scope. Use git status or internal session tracking to extract the explicit target list:

git status --porcelain | awk '{print $2}' | grep '\.py$'

Step 2: Targeted Automated Lint Correction

Execute the ruff lint engine using the explicit auto-fixer modifier, targeting only the space-separated list of file paths extracted in Step 1. Do not use a trailing dot (.):

uv run --locked ruff check --fix <path_to_modified_file_1> <path_to_modified_file_2>

Step 3: Targeted Code Layout Standardisation

Execute the native code formatter over only the identified target file paths to adjust line spacing, wrapping bounds, indentation, and quote alignments to match our 88-character rule baseline:

uv run --locked ruff format <path_to_modified_file_1> <path_to_modified_file_2>