@garygentry/feature-forge0.3.11
Cross-agent installer for the feature-forge skill suite — installs the canonical forge pipeline into Claude, Codex, Copilot, Cursor, Gemini, or Pi.
Untested on omp
This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.
Reports 0
No reports yet.
Readme
@garygentry/feature-forge
Cross-agent installer for the feature-forge skill suite — an end-to-end feature-development pipeline that runs on any coding agent (Claude, Codex, Copilot, Cursor, Gemini, or Pi).
This package installs the canonical forge skills into the agents detected on your machine. It is dependency-free and performs sandboxed, manifest-tracked writes.
Usage
# Install into every detected agent:
npx @garygentry/feature-forge install
# Scope to one agent:
npx @garygentry/feature-forge install -a codex
# Preview the plan without writing anything:
npx @garygentry/feature-forge install --dry-run --json
Commands
| Command | Description |
|---|---|
install (add) |
Install feature-forge into the target agent(s). |
update |
Reconcile an existing install to the current adapters. |
uninstall (remove) |
Remove a prior install (manifest-tracked files only). |
list (ls) |
Report per-agent detected / installed / up-to-date status. |
Common flags
| Flag | Description |
|---|---|
-a, --agent <id> |
Scope to one agent (claude/codex/copilot/cursor/gemini/pi). |
-g, --global |
Install into the user-level config dir (default: project-local). |
--symlink |
Symlink the bundle instead of copying (Windows always copies). |
--dry-run |
Print the planned actions without changing anything. |
--json |
Emit the run report as JSON. |
--skip-rauf |
Skip the rauf resolvability preflight (records raufPin: null). |
Per-agent install layout
Each agent's bundle is installed where that agent actually loads it (project scope shown; scope exceptions are noted below):
| Agent | Primary bundle | Second-root placement |
|---|---|---|
| claude | .claude/skills/feature-forge/ |
— |
| codex | .agents/skills/feature-forge/ |
.codex/agents/*.toml (custom agents, mirrored flat) |
| copilot | .github/feature-forge/ |
recursive .github/skills/, flat .github/agents/ |
| cursor | .cursor/rules/feature-forge/ |
— |
| gemini | .gemini/extensions/feature-forge/ |
— |
| pi | .pi/skills/feature-forge/ |
.pi/agents/*.md (custom agents, mirrored flat) |
For Pi, --global installs to ~/.pi/agent/skills/feature-forge/ and mirrors agents into
~/.pi/agent/agents/; project scope uses .pi/skills/feature-forge/ and .pi/agents/. The Pi
bundle includes real package.json metadata plus the AskUserQuestion compatibility extension;
run /trust (or use --approve in non-interactive tests) before relying on project-local Pi
resources.
For Copilot, --global installs one complete runtime bundle at
~/.copilot/feature-forge/ and native discovery mirrors at ~/.copilot/skills/ and
~/.copilot/agents/. Project scope keeps the complete runtime at .github/feature-forge/
alongside .github/skills/ and .github/agents/. Copilot loads the mirrored SKILL.md skills and
.agent.md custom agents natively; skills locate the runtime themselves (or via
FEATURE_FORGE_ROOT). Both scopes are runtime-verified on Copilot CLI 1.0.80. A direct install
exposes skills as /<name>. The installer is Copilot's compatibility path: the recommended route
is the Copilot plugin (copilot plugin marketplace add garygentry/feature-forge, then
copilot plugin install feature-forge@feature-forge), which exposes /feature-forge:<name>.
The installer no longer writes a block into .github/copilot-instructions.md. Installs made by
0.3.9 and earlier (runtime at .github/feature-forge/, personal installs under ~/.github/, plus
that block) are migrated by update -a copilot [-g], or by a plain update / update -g: the new
layout is applied and verified before the old recorded files are removed, and the block is stripped
only if unedited (--force strips an edited one; text outside the sentinels is always kept).
uninstall and list also find an old personal install under ~/.github/. See
docs/agents/copilot.md
for plugin vs direct installs, runtime roots, migration, diagnostics and uninstall.
Claude
Claude Code users can alternatively install via the plugin marketplace:
/plugin marketplace add garygentry/feature-forge
/plugin install feature-forge@feature-forge
Notes
The default loop runner is rauf, published as
@garygentry/rauf. The installer runs a
read-only resolvability preflight on the pin (@garygentry/rauf@0.19.0) and records it; pass
--skip-rauf to defer the check (e.g. offline installs). Install the rauf CLI itself with
npx @garygentry/rauf or its
binary script. See the
feature-forge README for the full
pipeline documentation and per-agent setup guides.
The installer never writes a forge.config.json — it deploys only the bundled skills and
runtime helpers. Configuration authorship belongs to /feature-forge:forge-init, which creates
the config and surfaces the auto-verify opt-in (whether to run forge-verify automatically after
each stage) at setup time.
License
MIT