formatting

Standardize whitespace, comments, imports, and LF line endings across Esposter source files.

23|3|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/Esposter/Esposter --skill formatting-esposter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formatting
Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/formatting
Command: npx skills add https://github.com/Esposter/Esposter --skill formatting-esposter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes code formatting across the project, reducing bikeshedding and merge conflicts by enforcing consistent whitespace, comments, import order, and line endings.

Core Features & Use Cases

  • Blank-line rules: avoid extra or missing blank lines between code blocks to improve readability and consistency.
  • Comment attachment: ensure comments attach directly to the code they describe and avoid unnecessary inline chatter.
  • Import grouping: keep value and type imports contiguous and separate groups with a single blank line.
  • Line endings: enforce LF endings across all tracked files to avoid cross-platform issues.

Quick Start

Run the formatting pass to align whitespace, comments, imports, and line endings across your codebase.

Frequently Asked Questions about formatting

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

FAQPage Schema
How do I enforce consistent code formatting for Vue components and TypeScript files?

Enforce consistent code formatting for Vue and TypeScript by standardizing whitespace, comments, import grouping, and LF line endings across all source files during development, review, and CI checks.

What is the best way to standardize import grouping and separation in a frontend codebase?

Standardize import grouping by keeping value and type imports contiguous and separating distinct import groups with a single blank line to improve readability and consistency across the codebase.

How do I enforce LF line endings across tracked files to avoid cross-platform issues?

Enforce LF line endings across all tracked files through a formatting pass that standardizes line endings, preventing cross-platform issues and reducing unnecessary merge conflicts in the repository.

Can I standardize Vue template spacing and blank-line placement between const assignments?

Yes, you can standardize Vue template spacing and enforce blank-line placement between consecutive const assignments to avoid extra or missing lines, improving overall code readability.

Why does consistent code formatting reduce bikeshedding and merge conflicts?

Consistent code formatting reduces bikeshedding and merge conflicts by enforcing uniform whitespace, comment attachment, and import order, eliminating subjective style debates and minimizing irrelevant diff noise.