Forge setup

Skill hiromaily/claude-forge/skills/forge-setup

Configure per-repository default flags for /forge pipelines. Interactive setup that saves preferences to .specs/preferences.json.From its SKILL.md

Install

npx -y skills add hiromaily/claude-forge --skill forge-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 455 tokens by cl100k_base, as published. Nobody here has run it

forge-setup

Configure default flags for /forge pipelines in this repository.

Flow

Call mcp__forge-state__preferences_get to load current preferences.

Present all current values and ask the user to confirm or change them using AskUserQuestion. Ask all five questions in a single prompt:

Current preferences:
- --auto (skip human confirmation): {current or "not set"}
- --debug (debug mode): {current or "not set"}
- --effort (default effort level): {current or "not set (auto-detect)"}
- --nopr (skip PR creation): {current or "not set"}
- --discuss (pre-pipeline discussion): {current or "not set"}

For each setting, reply with the desired value:
1. auto: yes / no / keep
2. debug: yes / no / keep
3. effort: S / M / L / none / keep
4. nopr: yes / no / keep
5. discuss: yes / no / keep

Parse the user's responses and build the preferences object.

Show a summary and ask for final confirmation:

Preferences to save:
- auto: true
- debug: false
- effort: M
- nopr: true
- discuss: false

Save these preferences? (yes/no)

If confirmed, call mcp__forge-state__preferences_set with the preferences object.
Display confirmation: "Preferences saved to .specs/preferences.json. These defaults will be applied to all future /forge runs. Explicit flags on /forge always override preferences."

Notes

"keep" means retain the current value (or "not set" if there is no current value).
"none" for effort means remove the preference (auto-detect effort).
This skill only reads/writes through MCP tools; it does not manipulate files directly.
Preferences can only enable flags. Setting a flag to "no" removes the preference (same as "not set").

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 455 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Load current preferences using the MCP tool
Parse the user responses into preferences

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.