skills/forge-config/SKILL.md
[writes] Edit Forge pipeline settings interactively. Use when changing framework, test runner, scoring thresholds, reviewer selection, convergence limits, or toggling features like caveman mode. Validates changes. Trigger: /forge-config, change settings, edit config, adjust thresholds, update scoring
npx skillsauth add quantumbitcz/dev-pipeline forge-configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
See shared/skill-contract.md for the standard exit-code table.
| Command | Action |
|---------|--------|
| /forge-config | Show current config summary |
| /forge-config set <key> <value> | Set a config value |
| /forge-config add <key> <value> | Add to list field (e.g., code_quality) |
| /forge-config remove <key> <value> | Remove from list field |
| /forge-config validate | Run validation (delegates to /forge-verify --config) |
| /forge-config show <section> | Show specific section (components, scoring, convergence, caveman) |
| /forge-config diff | Show changes since last pipeline run |
.claude/forge.local.md or .claude/forge-config.md exists. If neither: "No forge configuration found. Run /forge-init first." STOP..claude/forge.local.md and .claude/forge-config.md$ARGUMENTS (e.g., set components.testing vitest)${CLAUDE_PLUGIN_ROOT}/shared/validate-config.sh with the proposed changecomponents.* → forge.local.mdscoring.*, convergence.*, caveman.* → forge-config.md$ARGUMENTScode_quality)add: append value if not already presentremove: delete value if present, warn if not foundDelegates to /forge-verify --config skill. Shows results inline.
forge.local.md and forge-config.md.forge/state.json (if exists).forge/state.json: show "No previous run to compare against"<!-- locked --> fences in forge-config.md cannot be modified. Show: "This value is locked. Remove the <!-- locked --> fence to unlock."set/add/remove operation runs validation before applying| Condition | Action | |-----------|--------| | Config file missing | Suggest: "Run /forge-init first" | | Invalid key path | Show valid keys from config-schema.json | | Invalid value | Show valid values with fuzzy suggestion | | Locked section | Refuse edit, explain how to unlock |
/forge-verify --config — validate config without editing/forge-init — initial project setup/forge-help — find the right skilldevelopment
[writes] Build, fix, deploy, review, or modify code in this project. Universal entry for the forge pipeline. Auto-bootstraps on first run; brainstorms before planning when given a feature description. Use when you want to take any productive action: implementing features, fixing bugs, reviewing branches, deploying, committing, running migrations.
tools
[writes] Manage forge state and configuration: recovery, abort, config edits, session handoff, automations, playbooks, output compression, knowledge graph maintenance. Use when you need to recover from broken pipeline state, edit settings, or manage long-lived state.
development
[writes] Create, list, show, resume, or search forge session handoffs. Use when context is getting heavy and you want to transfer a forge run or conversation into a fresh Claude Code session, or to resume from a prior handoff artefact. Subcommands - no args (write), list, show, resume, search.
development
[writes] Manage the Neo4j knowledge graph. Subcommands: init, rebuild (writes); status, query <cypher>, debug (read-only). Requires Docker. No default — an explicit subcommand is required. Use when setting up the graph for the first time, rebuilding after major refactors, checking graph health, or running ad-hoc Cypher diagnostics.