---
name: hforge-refresh
description: refresh shared runtime summaries and generated harness forge artifacts after install changes, repo changes, or stale analysis state. use when the runtime is present but outdated, incomplete, or no longer trustworthy.
HForge Refresh
Trigger Signals
runtime summaries are stale after installs or content changes
repo-intelligence artifacts no longer match the current repository state
the user explicitly asks to refresh the project-owned runtime
a later review or analysis should not rely on outdated runtime state
Inspect First
.hforge/runtime/index.json
.hforge/generated/agent-command-catalog.json
.hforge/runtime/repo/
Workflow
run hforge refresh --root . --json
follow with hforge status --root . --json when install-state confirmation matters
summarize regenerated artifacts, remaining gaps, and the best next action
Output Contract
confirmation that refresh ran or why it could not
refreshed runtime artifacts and any remaining missing prerequisites
the next command to run, usually /hforge-analyze or /hforge-review
Validation Path
hforge refresh --root . --json
hforge status --root . --json
Failure Modes
the repo is not initialized
required runtime files or launchers are missing
refresh cannot reconcile the current install state
Escalation
escalate when refresh cannot complete without a fresh bootstrap
escalate when runtime summaries regenerate but still disagree with the repo
1---2name: hforge-refresh3description: ---4---5---6name: hforge-refresh7description: refresh shared runtime summaries and generated harness forge artifacts after install changes, repo changes, or stale analysis state. use when the runtime is present but outdated, incomplete, or no longer trustworthy.8---910# HForge Refresh1112## Trigger Signals1314- runtime summaries are stale after installs or content changes15- repo-intelligence artifacts no longer match the current repository state16- the user explicitly asks to refresh the project-owned runtime17- a later review or analysis should not rely on outdated runtime state1819## Inspect First2021- `.hforge/runtime/index.json`22- `.hforge/generated/agent-command-catalog.json`23- `.hforge/runtime/repo/`2425## Workflow26271. run `hforge refresh --root . --json`282. follow with `hforge status --root . --json` when install-state confirmation matters293. summarize regenerated artifacts, remaining gaps, and the best next action3031## Output Contract3233- confirmation that refresh ran or why it could not34- refreshed runtime artifacts and any remaining missing prerequisites35- the next command to run, usually `/hforge-analyze` or `/hforge-review`3637## Validation Path3839- `hforge refresh --root . --json`40- `hforge status --root . --json`4142## Failure Modes4344- the repo is not initialized45- required runtime files or launchers are missing46- refresh cannot reconcile the current install state4748## Escalation4950- escalate when refresh cannot complete without a fresh bootstrap51- escalate when runtime summaries regenerate but still disagree with the repo5253## References5455- `skills/hforge-refresh/references/refresh-order.md`56- `skills/hforge-refresh/references/output-contract.md`
Run npx skillmds@latest add ldilov/hforge-refresh 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