forgelisted

# /forge — dotforge bridge for OpenClaw Execute dotforge configuration management commands from any OpenClaw channel (WhatsApp, Telegram, Slack, etc.). ## How it works This skill bridges OpenClaw to dotforge by running `claude` CLI in the target project directory. All `/forge` subcommands are available. ## Environment - `DOTFORGE_DIR` — path to dotforge repo (required) - Default project: uses `DOTFORGE_DIR` itself if no project specified ## Command format ``` /forge <command> [project:<name>] ``` If `project:<name>` is provided, look up the project path from `$DOTFORGE_DIR/registry/projects.yml` and execute in that directory. If no project specified, use current context or ask the user. ## Available commands ### Read-only (safe from any channel) | Command | What it does | |---------|-------------| | `status` | Multi-project dashboard with scores and trends | | `version` | Show dotforge version | | `pipeline` | Practices lifecycle status | | `inbox` | List pending practices | ### Per-project (require project context) | Command | What it does | |---------|-------------| | `audit` | Score project configuration 0-10 | | `diff` | Show pending changes since last sync | | `insights` | Analyze past sessions | | `rule-check` | Detect inert rules | ### Mutation (ask for confirmation before executing) | Command | What it does | |---------|-------------| | `sync` | Update project config against template | | `bootstrap` | Initialize .claude/ in a project | | `capture "text"