eforge-config

> **Note:** In Pi, the native `/eforge:config` command provides a richer interactive experience with a structured TUI panel viewer. This skill serves as a fallback for non-interactive contexts and as model-readable documentation. # /eforge:config Create or modify an `eforge/config.yaml` configuration file interactively. Supports two modes - init for new projects and edit for existing configs. Validation uses the eforge daemon. `eforge/config.yaml` holds **team-wide settings only** (postMergeCommands, agent tuning, hooks, queue config, etc.). Personal dev overrides can be placed in `.eforge/config.yaml` (gitignored, highest priority) - it deep-merges over the project and user tiers. Agent runtime profiles live in named profile files (`.eforge/profiles/<name>.yaml` for project-local scope, `eforge/profiles/<name>.yaml` for project scope, or `~/.config/eforge/profiles/<name>.yaml` for user scope) and are managed by `/eforge:init` and `/eforge:profile-new`. ## Mode Detection Determine the mode from arguments and file state: 1. If `$ARGUMENTS` contains `--init`, use **init mode** 2. If `$ARGUMENTS` contains `--edit`, use **edit mode** 3. If `eforge/config.yaml` exists in the project root, use **edit mode** 4. Otherwise, use **init mode** ## Init Mode ### Step 1: Check Existence If `eforge/config.yaml` already exists, ask the user whether they want to switch to edit mode or overwrite. Respect their choice. ### Step 2: Require an active agent runtime profile This skill do...