acquire-codebase-knowlโฆ
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts likeโฆ
Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.
Claude Code
$ npx -y skills add github/awesome-copilot --skill editorconfig --agent claude-code
Codex
$ npx skills add github/awesome-copilot --skill editorconfig -a codex -y
Cursor
$ npx skills add github/awesome-copilot --skill editorconfig -a cursor -y
Gemini CLI
$ npx skills add github/awesome-copilot --skill editorconfig -a gemini-cli -y
GitHub Copilot
$ npx skills add github/awesome-copilot --skill editorconfig -a github-copilot -y
OpenCode
$ npx skills add github/awesome-copilot --skill editorconfig -a opencode -y
Windsurf
$ npx skills add github/awesome-copilot --skill editorconfig -a windsurf -y
name: editorconfig description: 'Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.'
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.
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:
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.
Here is the `.editorconfig` file tailored to your project:
# .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
A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts likeโฆ
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wrapsโฆ
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default,โฆ
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks,โฆ
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts likeโฆ
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoidโฆ
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AIโฆ