generate-editorconfig-by-techstack

Generate or merge .editorconfig sections by detecting project technology stacks.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/CloudyWing/ai-dotfiles --skill generate-editorconfig-by-techstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-editorconfig-by-techstack
Source: https://github.com/CloudyWing/ai-dotfiles/tree/main/skills/generate-editorconfig-by-techstack
Command: npx skills add https://github.com/CloudyWing/ai-dotfiles --skill generate-editorconfig-by-techstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating or completing a project's .editorconfig by detecting the repository's languages and common tools, reducing manual configuration and inconsistent editor settings across contributors.

Core Features & Use Cases

  • Automatic detection: Scans the project root for manifests and file patterns (package.json, tsconfig.json, *.csproj, pyproject.toml, go.mod, Dockerfile, *.md, etc.) to infer relevant editorconfig sections.
  • Non-destructive merge: Reads an existing .editorconfig and appends missing sections without overwriting user customizations.
  • Opinionated defaults: Applies a global base block plus language-specific blocks (C#, Python, Go, Markdown, YAML/JSON/TOML, PowerShell, CSV, Shell, Dockerfile) to standardize formatting.
  • Use Case: Standardize editor settings for a mixed-language repository before onboarding new contributors or when consolidating dotfiles.

Quick Start

Run the skill to scan the repository root and generate or merge a .editorconfig tailored to the detected tech stack, then review the reported added and skipped sections.

Frequently Asked Questions about generate-editorconfig-by-techstack

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

FAQPage Schema
How do I generate an .editorconfig based on my project's tech stack?

To generate an .editorconfig, this Skill scans your repository root for manifests like package.json, tsconfig.json, pyproject.toml, and Dockerfile, then applies opinionated language-specific formatting blocks to create or update the file automatically.

Can I merge new editorconfig settings without overwriting my existing customizations?

Yes, you can merge editorconfig settings non-destructively; this Skill reads existing configurations and appends only missing file-type sections while preserving your current user customizations and reporting skipped sections.

Does the editorconfig generator support mixed-language repositories with C#, Python, and Go?

Yes, the editorconfig generator detects mixed-language stacks from manifests like *.csproj, pyproject.toml, and go.mod, inserting global base blocks alongside language-specific blocks for C#, Python, Go, and more.

What is the best way to standardize code style across a repository before onboarding contributors?

The best way to standardize code style is to auto-generate a complete .editorconfig tailored to your detected tools and languages, ensuring consistent editor settings across all contributors without manual configuration.

Why are some file-type sections skipped when generating my .editorconfig?

File-type sections are skipped during generation if they already exist in your current .editorconfig, ensuring the non-destructive merge process preserves your predefined user customizations without duplicating settings.

When do I need an .editorconfig for my project?

You need an .editorconfig when standardizing formatting across tools and IDEs for languages like TypeScript, C#, Python, or Go, reducing inconsistent editor settings and manual configuration for contributors.