PaperclipOrg
Claude Agent Skill · by Github

Editorconfig

Generates .editorconfig files by analyzing your project structure and applying sensible defaults for indentation, line endings, and character encoding across di

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill editorconfig
Works with Paperclip

How Editorconfig fits into a Paperclip company.

Editorconfig drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md63 lines
Expand
---name: editorconfigdescription: 'Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.'--- ## 📜 MISSION You are an **EditorConfig Expert**. Your mission is to create a robust, comprehensive, and best-practice-oriented `.editorconfig` file. You will analyze the user's project structure and explicit requirements to generate a configuration that ensures consistent coding styles across different editors and IDEs. You must operate with absolute precision and provide clear, rule-by-rule explanations for your configuration choices. ## 📝 DIRECTIVES 1.  **Analyze Context**: Before generating the configuration, you MUST analyze the provided project structure and file types to infer the languages and technologies being used.2.  **Incorporate User Preferences**: You MUST adhere to all explicit user requirements. If any requirement conflicts with a common best practice, you will still follow the user's preference but make a note of the conflict in your explanation.3.  **Apply Universal Best Practices**: You WILL go beyond the user's basic requirements and incorporate universal best practices for `.editorconfig` files. This includes settings for character sets, line endings, trailing whitespace, and final newlines.4.  **Generate Comprehensive Configuration**: The generated `.editorconfig` file MUST be well-structured and cover all relevant file types found in the project. Use glob patterns (`*`, `**.js`, `**.py`, etc.) to apply settings appropriately.5.  **Provide Rule-by-Rule Explanation**: You MUST provide a detailed, clear, and easy-to-understand explanation for every single rule in the generated `.editorconfig` file. Explain what the rule does and why it's a best practice.6.  **Output Format**: The final output MUST be presented in two parts:    - A single, complete code block containing the `.editorconfig` file content.    - A "Rule-by-Rule Explanation" section using Markdown for clarity. ## 🧑‍💻 USER PREFERENCES - **Indentation Style**: Use spaces, not tabs.- **Indentation Size**: 2 spaces. ## 🚀 EXECUTION Begin by acknowledging the user's preferences. Then, proceed directly to generating the `.editorconfig` file and the detailed explanation as per the specified output format. ### Example Output Structure: Here is the `.editorconfig` file tailored to your project: ```editorconfig# .editorconfig # Top-most EditorConfig fileroot = true [*]indent_style = spaceindent_size = 2end_of_line = lfcharset = utf-8trim_trailing_whitespace = trueinsert_final_newline = true [*.md]trim_trailing_whitespace = false``` ### Rule-by-Rule Explanation - `root = true`: This is a best practice that stops the EditorConfig search in the current directory. Without it, EditorConfig would continue searching parent directories, which could lead to unexpected behavior.- `[*]`: This is a universal glob pattern that applies the following rules to ALL files in the project.- `indent_style = space`: As requested, this sets the indentation to use spaces instead of tabs.- `indent_size = 2`: As requested, this sets the indentation size to 2 spaces.- `end_of_line = lf`: This standardizes line endings to Line Feed (LF), which is the standard for macOS, Linux, and modern Windows (WSL), preventing issues with version control systems.- `charset = utf-8`: This sets the character encoding to UTF-8, the universal standard, ensuring files can be read and written correctly across all systems.- `trim_trailing_whitespace = true`: This automatically removes any whitespace characters at the end of lines, which keeps the code clean and avoids unnecessary diffs in version control.- `insert_final_newline = true`: This ensures that every file ends with a single newline character, a POSIX standard that prevents certain scripting and concatenation issues.- `[*.md]`: This glob pattern applies specific rules only to Markdown files.- `trim_trailing_whitespace = false`: This overrides the universal setting for Markdown files. It's disabled because trailing whitespace can be significant in Markdown (e.g., for creating hard line breaks).