configure-editor
EditorConfig and VS Code workspace settings for team consistency. Use when setting up format-on-save, recommended extensions, or debug configurations.
How do I install this agent skill?
npx skills add https://github.com/laurigates/claude-plugins --skill configure-editorIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is safe and provides legitimate functionality for standardizing editor configurations (EditorConfig and VS Code) within a project. It uses local shell commands to detect project structure and applies pre-defined templates from its reference documentation without executing remote code or exfiltrating data.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1/2 files flagged
What does this agent skill do?
/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 team | Personal editor preferences only (configure in user settings) |
| Checking EditorConfig or VS Code workspace compliance | Just viewing existing .editorconfig (use Read tool) |
| Configuring format-on-save for detected languages | Project doesn't use VS Code (configure for other editors manually) |
| Adding recommended VS Code extensions for project tools | Extensions are already properly configured |
| Setting up debug configurations and tasks | Simple 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:
| Indicator | Language/Tool | Configuration Needed |
|---|---|---|
package.json | JavaScript/TypeScript | Biome |
tsconfig.json | TypeScript | TypeScript extension |
pyproject.toml | Python | Ruff, Python extension |
Cargo.toml | Rust | rust-analyzer |
biome.json | Biome formatter/linter | Biome extension |
Step 2: Analyze current editor configuration
Check existing configuration against these requirements:
EditorConfig:
- Verify
.editorconfigexists - Check root directive, charset, end-of-line, final newline, trim whitespace
- Check language-specific sections match detected languages
VS Code Settings:
- Verify
.vscode/settings.jsonexists - Check format-on-save, default formatters per language, language-specific settings
VS Code Extensions:
- Verify
.vscode/extensions.jsonexists - 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.
- Create or update
.editorconfigwith language-specific sections - Create or update
.vscode/settings.jsonwith format-on-save and per-language formatters - Create or update
.vscode/extensions.jsonwith recommended extensions for detected tools - Add language-specific settings (TypeScript import preferences, Python interpreter, Rust clippy)
Step 5: Create launch and task configurations
- Create
.vscode/launch.jsonwith debug configurations for detected languages - Create
.vscode/tasks.jsonwith 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
| Context | Command |
|---|---|
| Check if EditorConfig exists | test -f .editorconfig && echo "exists" || echo "missing" |
| Validate EditorConfig syntax | editorconfig-checker .editorconfig 2>&1 (if installed) |
| Check VS Code settings exist | test -f .vscode/settings.json && jq empty .vscode/settings.json 2>&1 |
| List detected languages | find . -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
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply 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
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/laurigates/claude-plugins/configure-editor">View configure-editor on skillZs</a>