# Editorconfig

> Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.

- **Type:** Skill
- **Install:** `agentstack add skill-cogni-ai-ou-cogni-ai-agent-skills-editorconfig`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Cogni-AI-OU](https://agentstack.voostack.com/s/cogni-ai-ou)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Cogni-AI-OU](https://github.com/Cogni-AI-OU)
- **Source:** https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/editorconfig

## Install

```sh
agentstack add skill-cogni-ai-ou-cogni-ai-agent-skills-editorconfig
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# editorconfig

Generate a robust, comprehensive, and best-practice-oriented `.editorconfig` file to ensure consistent coding styles across different editors and IDEs.

## Core Process

1. **Analyze Context**: Scan the project structure and file types to infer the languages and technologies being used.
2. **Incorporate Preferences**: Adhere to explicit user constraints (e.g., indentation style/size). Note any conflicts with best practices in the final explanation.
3. **Apply Universal Best Practices**: Enforce baseline standards (character sets, LF line endings, trailing whitespace, and final newlines).
4. **Generate File**: Output a structured `.editorconfig` file covering all relevant file types found in the project via glob patterns (`*`, `**.js`, `**.py`, etc.).
5. **Provide Explanations**: Detail the rationale for every single rule generated in a clear Markdown "Rule-by-Rule Explanation" section below the code block.

## Core Principles

- **Precision Targeting**: Apply rules via universal and specific glob patterns without polluting unrelated scopes.
- **Universal Standards**: Use `lf` for line endings, `utf-8` charset, trim trailing whitespace, and insert final newlines globally unless context demands otherwise.
- **Exceptions Mapping**: Explicitly disable `trim_trailing_whitespace` for `[*.md]` files since trailing whitespace holds semantic meaning (hard line breaks).

## When to Use

- When requested to generate, update, or configure an `.editorconfig` file.
- When standardizing coding styles or formatting hooks for a workspace.

## When Not to Use

- When the project already has an established `.editorconfig` that simply needs minor adjustments (edit the existing file rather than generating a new one from scratch).
- For enforcing complex logic constraints or code quality metrics (use Linters like ESLint or Pylint instead).
- If the repository strictly uses an automated formatter like Prettier or Black that overrides editor configurations.

## Common Pitfalls

- **Overriding Markdown Semantics**: Setting `trim_trailing_whitespace = true` globally without adding an exception for `[*.md]`, breaking Markdown's hard-line breaks (which require two trailing spaces).
- **Ignoring Project Context**: Generating a generic `.editorconfig` that defaults to 4 spaces, even when every file in the current repository clearly uses 2 spaces.
- **Missing `root = true`**: Forgetting to add `root = true` at the top of the file, causing editors to continue searching parent directories for conflicting rules.

## Quick Start

```editorconfig
# Top-most EditorConfig file
root = true

[*]
indent_style = space
indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false
```

## Diagnostics and Troubleshooting

- If settings are overridden by parent directories, verify that `root = true` is placed at the top of the file.
- If whitespace handling causes issues in Markdown or Makefiles, explicitly add overrides for `[*.md]` or `[Makefile]`.

## Best Practices

- Start with `root = true` to stop the EditorConfig search in the current directory.
- Combine the output into two parts: A single code block with the `.editorconfig` and a "Rule-by-Rule Explanation" section in Markdown.

## What to Avoid

- Outputting an `.editorconfig` without rule-by-rule explanations.
- Overwriting existing `.editorconfig` files blindly without reading and merging current project conventions.

## References

-

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Cogni-AI-OU](https://github.com/Cogni-AI-OU)
- **Source:** [Cogni-AI-OU/cogni-ai-agent-skills](https://github.com/Cogni-AI-OU/cogni-ai-agent-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-cogni-ai-ou-cogni-ai-agent-skills-editorconfig
- Seller: https://agentstack.voostack.com/s/cogni-ai-ou
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.