enforce-ide

Generate baseline .editorconfig and VS Code settings aligned with repository standards.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill enforce-ide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enforce-ide
Source: https://github.com/leocosta/octopus/tree/main/skills/enforce-ide
Command: npx skills add https://github.com/leocosta/octopus --skill enforce-ide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a baseline .editorconfig and (opt-in) .vscode/ settings + extensions aligned with the project's formatter and linter — the editor layer between keystroke and commit. Detects stack via file extensions; merges keys conservatively, never overwrites a user value. Pairs with enforce-precommit and the guardrails bundle.

Core Features & Use Cases

  • Establishes a baseline editor configuration by generating a baseline .editorconfig and optional .vscode/ settings and extensions that align with the repository standards.
  • Detects project stacks from file extensions and manifests to apply stack-aware defaults without overwriting user customizations.
  • Merges configurations conservatively, preserving existing values and only adding missing keys or sections.
  • Integrates with guardrails and precommit to enforce editor consistency across local and CI environments.

Quick Start

Run the enforce-ide workflow after enabling guardrails to generate the baseline IDE configuration.

Frequently Asked Questions about enforce-ide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize VS Code settings and .editorconfig across a repository?

Standardize VS Code settings and .editorconfig by generating a baseline editor configuration that aligns with repository standards. The process detects project stacks from file extensions and applies stack-aware defaults without overwriting existing user customizations.

What's the best way to enforce editor consistency without losing developer customizations?

Enforce editor consistency by merging configurations conservatively. The mechanism preserves existing values and only adds missing keys or sections, ensuring user customizations remain intact while applying stack-aware defaults to missing configuration entries.

Does this IDE configuration approach work with precommit hooks and guardrails?

Yes, the IDE configuration integrates with enforce-precommit and the guardrails bundle. This integration enforces editor consistency across both local development environments and CI pipelines, aligning the editor layer between keystroke and commit.

How does stack-aware editor configuration detection work?

Stack-aware editor configuration detection works by analyzing file extensions and manifests in the repository. Based on the detected project stacks, it applies appropriate default editor settings and configurations tailored to the specific technologies used.

Can I generate VS Code extensions and settings alongside .editorconfig?

Yes, you can generate optional .vscode/ settings and extensions alongside a baseline .editorconfig. This opt-in feature aligns the VS Code environment with the project's formatter and linter, creating a consistent editor layer across the development team.