---
name: hforge-init
description: initialize harness forge in the current repository, bootstrap the target-aware runtime, and establish the managed surfaces needed for later review, analysis, and decision tracking. use when the repo is not initialized, when runtime files are missing, or when the user asks to set up hforge in a project.
HForge Init
Trigger Signals
the repository is not yet initialized for Harness Forge
.hforge/agent-manifest.json or .hforge/runtime/index.json is missing
target runtime files such as .codex/ or .claude/ are missing or incomplete
the user asks to initialize, bootstrap, or wire Harness Forge into a repo
Inspect First
repository root files such as README.md, package.json, and CI or target config files
AGENTS.md and .agents/skills/ when present
.hforge/agent-manifest.json and .hforge/runtime/index.json when present
.codex/ and .claude/ bridge surfaces when present
Workflow
inspect the current workspace state with hforge status --root . --json
if the repo is not initialized or target runtime files are absent, run hforge bootstrap --root . --yes
run hforge refresh --root . --json after bootstrap so shared runtime summaries are current
inspect hforge catalog --json when bundle or profile visibility matters
summarize detected targets, installed surfaces, runtime artifacts, and the recommended next command
Output Contract
initialization status and whether bootstrap was needed
detected targets and managed runtime surfaces now present
runtime artifacts now available under .hforge/runtime/
the best next command to run, such as /hforge-analyze or /hforge-review
Validation Path
hforge status --root . --json
hforge bootstrap --root . --yes
hforge refresh --root . --json
Failure Modes
the repo is not writable
the hforge launcher is not available
target detection is incomplete or no supported target is installed yet
Escalation
escalate when bootstrap cannot write the project-owned runtime
escalate when targets are ambiguous and the repo needs explicit operator intent
escalate when package installation or shell setup is missing
References
skills/hforge-init/references/bootstrap-order.md
skills/hforge-init/references/output-contract.md
1---2name: hforge-init3description: ---4---5---6name: hforge-init7description: initialize harness forge in the current repository, bootstrap the target-aware runtime, and establish the managed surfaces needed for later review, analysis, and decision tracking. use when the repo is not initialized, when runtime files are missing, or when the user asks to set up hforge in a project.8---910# HForge Init1112## Trigger Signals1314- the repository is not yet initialized for Harness Forge15- `.hforge/agent-manifest.json` or `.hforge/runtime/index.json` is missing16- target runtime files such as `.codex/` or `.claude/` are missing or incomplete17- the user asks to initialize, bootstrap, or wire Harness Forge into a repo1819## Inspect First2021- repository root files such as `README.md`, `package.json`, and CI or target config files22- `AGENTS.md` and `.agents/skills/` when present23- `.hforge/agent-manifest.json` and `.hforge/runtime/index.json` when present24- `.codex/` and `.claude/` bridge surfaces when present2526## Workflow27281. inspect the current workspace state with `hforge status --root . --json`292. if the repo is not initialized or target runtime files are absent, run `hforge bootstrap --root . --yes`303. run `hforge refresh --root . --json` after bootstrap so shared runtime summaries are current314. inspect `hforge catalog --json` when bundle or profile visibility matters325. summarize detected targets, installed surfaces, runtime artifacts, and the recommended next command3334## Output Contract3536- initialization status and whether bootstrap was needed37- detected targets and managed runtime surfaces now present38- runtime artifacts now available under `.hforge/runtime/`39- the best next command to run, such as `/hforge-analyze` or `/hforge-review`4041## Validation Path4243- `hforge status --root . --json`44- `hforge bootstrap --root . --yes`45- `hforge refresh --root . --json`4647## Failure Modes4849- the repo is not writable50- the `hforge` launcher is not available51- target detection is incomplete or no supported target is installed yet5253## Escalation5455- escalate when bootstrap cannot write the project-owned runtime56- escalate when targets are ambiguous and the repo needs explicit operator intent57- escalate when package installation or shell setup is missing5859## References6061- `skills/hforge-init/references/bootstrap-order.md`62- `skills/hforge-init/references/output-contract.md`
Run npx skillmds@latest add ldilov/hforge-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
--- It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ldilov (@ldilov) published this skill. Their other Agent Skills are listed on their SkillMD profile.
ldilov