Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
laurigates avatar

Configure Editor

  • 54 installs
  • 49 repo stars
  • Updated August 4, 2026
  • laurigates/claude-plugins

Helps with ai & agent building tasks.

About

configure-editor is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • configure-editor
  • AI & Agent Building
  • AI-coding skill

Configure Editor by the numbers

  • 54 all-time installs (skills.sh)
  • Ranked #6,877 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/laurigates/claude-plugins --skill configure-editor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs54
repo stars49
Last updatedAugust 4, 2026
Repositorylaurigates/claude-plugins

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

/configure:editor

Check and configure editor settings for consistency across the team.

When to Use This Skill

Use this skill when...Use another approach when...
Setting up consistent editor configuration across a teamPersonal editor preferences only (configure in user settings)
Checking EditorConfig or VS Code workspace complianceJust viewing existing .editorconfig (use Read tool)
Configuring format-on-save for detected languagesProject doesn't use VS Code (configure for other editors manually)
Adding recommended VS Code extensions for project toolsExtensions are already properly configured
Setting up debug configurations and tasksSimple project with no debugging needs

Context

  • EditorConfig: !find . -maxdepth 1 -name \'.editorconfig\'
  • VS Code settings: !find . -maxdepth 1 -name \'.vscode/settings.json\'
  • VS Code extensions: !find . -maxdepth 1 -name \'.vscode/extensions.json\'
  • VS Code launch: !find . -maxdepth 1 -name \'.vscode/launch.json\'
  • VS Code tasks: !find . -maxdepth 1 -name \'.vscode/tasks.json\'
  • Project languages: !find . -maxdepth 1 \( -name 'package.json' -o -name 'tsconfig.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'biome.json' \)
  • Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'

Parameters

Parse from $ARGUMENTS:

  • --check-only: Report compliance status without modifications
  • --fix: Apply all fixes automatically without prompting

Execution

Execute this editor configuration workflow:

Step 1: Detect project languages and tools

Check for language indicators:

IndicatorLanguage/ToolConfiguration Needed
package.jsonJavaScript/TypeScriptBiome
tsconfig.jsonTypeScriptTypeScript extension
pyproject.tomlPythonRuff, Python extension
Cargo.tomlRustrust-analyzer
biome.jsonBiome formatter/linterBiome extension

Step 2: Analyze current editor configuration

Check existing configuration against these requirements:

EditorConfig: 1. Verify .editorconfig exists 2. Check root directive, charset, end-of-line, final newline, trim whitespace 3. Check language-specific sections match detected languages

VS Code Settings: 1. Verify .vscode/settings.json exists 2. Check format-on-save, default formatters per language, language-specific settings

VS Code Extensions: 1. Verify .vscode/extensions.json exists 2. Check recommended extensions match project tools

Step 3: Generate compliance report

Print a formatted compliance report showing status of each check:

Editor Configuration Compliance Report
=======================================
Project: [name]
Languages: [detected]
Detected Tools: [detected]

EditorConfig:     [status per check]
VS Code Settings: [status per check]
VS Code Extensions: [status per check]

Overall: [X issues found]
Recommendations: [list specific fixes]

If --check-only, stop here.

Step 4: Configure editor files (if --fix or user confirms)

Apply fixes based on detected languages. Use configurations from REFERENCE.md.

1. Create or update .editorconfig with language-specific sections 2. Create or update .vscode/settings.json with format-on-save and per-language formatters 3. Create or update .vscode/extensions.json with recommended extensions for detected tools 4. Add language-specific settings (TypeScript import preferences, Python interpreter, Rust clippy)

Step 5: Create launch and task configurations

1. Create .vscode/launch.json with debug configurations for detected languages 2. Create .vscode/tasks.json with build/test/lint tasks

Step 6: Update standards tracking

Update .project-standards.yaml:

components:
  editor: "2025.1"
  editor_config: true
  vscode_settings: true
  vscode_extensions: true

Step 7: Create documentation

Create docs/EDITOR_SETUP.md with quick start instructions for the team covering VS Code setup, recommended extensions, and troubleshooting.

Step 8: Print completion report

Print a summary of all changes made, including files created/updated, extensions recommended, and next steps for the team.

For detailed configuration templates and language-specific settings, see REFERENCE.md.

Agentic Optimizations

ContextCommand
Check if EditorConfig exists`test -f .editorconfig && echo "exists" \
Validate EditorConfig syntaxeditorconfig-checker .editorconfig 2>&1 (if installed)
Check VS Code settings existtest -f .vscode/settings.json && jq empty .vscode/settings.json 2>&1
List detected languagesfind . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \) -exec basename {} \;
Quick compliance check/configure:editor --check-only
Auto-fix all issues/configure:editor --fix

Flags

FlagDescription
--check-onlyReport status without offering fixes
--fixApply all fixes automatically without prompting

Examples

# Check compliance and offer fixes
/configure:editor

# Check only, no modifications
/configure:editor --check-only

# Auto-fix all issues
/configure:editor --fix

Error Handling

  • No language detected: Create minimal EditorConfig
  • Conflicting formatters: Warn about duplicate formatter configs
  • Invalid JSON: Report parse error, offer to replace with template

See Also

  • /configure:formatting - Configure code formatting
  • /configure:linting - Configure linting tools
  • /configure:all - Run all compliance checks
  • EditorConfig documentation: https://editorconfig.org
  • VS Code settings reference: https://code.visualstudio.com/docs/getstarted/settings

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.