Hforge init

Skill ldilov/harness-forge/skills/hforge-init

AI coding agent runtime that makes LLMs understand your codebase with repository-aware context, memory, and continuous learning

Install

npx -y skills add ldilov/harness-forge --skill hforge-init

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

3 stars3 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.3 KB, as published. Nobody here has run it

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