Generate a root .editorconfig with indentation and line-ending rules.
npx skills add https://github.com/aspiers/ai-config --skill editorconfig
Please help me install this Agent Skill. Skill: editorconfig Source: https://github.com/aspiers/ai-config/tree/main/.claude/skills/editorconfig Command: npx skills add https://github.com/aspiers/ai-config --skill editorconfig
This Skill creates a minimal, consistent .editorconfig file for a repository, helping teams enforce formatting rules automatically.
Create a minimal .editorconfig file at the repository root that matches the project's existing style
High-intent search queries and answers about installing and using this skill.
To generate a .editorconfig, the Skill analyzes existing indentation, line endings, and file types to infer sensible defaults. It then writes a minimal configuration file with universal settings and file-type overrides directly to the repository root.
Enforcing consistent indentation and line endings is achieved by generating a root .editorconfig with file-type overrides. The Skill detects existing repository style and writes universal formatting rules to standardize editor behavior across languages.
Yes, you can retrofit an existing codebase by detecting its current indentation and line ending conventions. The Skill analyzes the repository's existing style to generate a minimal .editorconfig that matches your established formatting rules.
You need an .editorconfig during project setup or when retrofitting a repo to standardize editor behavior. It helps teams enforce formatting rules automatically by ensuring consistent indentation and line endings across different editors and file types.
Yes, the generated .editorconfig supports file-type overrides. The Skill writes a root-level configuration that includes universal settings alongside specific overrides to standardize editor behavior across various languages in your repository.
Your team needs an .editorconfig to automatically enforce formatting rules across different editors. While guidelines are manual, a generated .editorconfig standardizes indentation and line endings automatically, ensuring consistent editor behavior without relying on individual developer configurations.
ehtbantonGenerate .editorconfig files for consistent coding styles across editors.
avvaleValidate commit messages against the Conventional Commits specification.
MolcajeteAIConfigure Husky and lint-staged pre-commit hooks for automated code quality checks.
ruchernchongApply Biome linting and formatting to JavaScript/TypeScript projects.
