skills.rest
ldilov
ldilovCOMMUNITY
Explore all skills by this author →
GitHub

hforge-refresh

Regenerate Harness Forge runtime summaries and report changes after updates.

3|Updated Mar 24, 2026
Search Tags:#automation#cli#runtime#refresh#repo-state#harness-forge
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill hforge-refresh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hforge-refresh
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/hforge-refresh
Command: npx skills add https://github.com/ldilov/harness-forge --skill hforge-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate Harness Forge runtime summaries and report what changed after install changes, content updates, or stale repo-intelligence artifacts.

Core Features & Use Cases

  • Regenerate shared runtime summaries after changes
  • Report changes and prerequisites, guiding next steps
  • Handle uninitialized repos by suggesting initialization

Quick Start

Execute the refresh workflow to update runtime state after install changes or content updates.

Frequently Asked Questions about hforge-refresh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refresh Harness Forge runtime state after updating repository content?▼

To refresh Harness Forge runtime state, run the hforge refresh command with the --root and --json flags. This regenerates runtime summaries, reports changed artifacts, and provides next actions for the repository.

Why are my Harness Forge runtime summaries stale after install changes?▼

Harness Forge runtime summaries become stale after install changes or content updates because the underlying artifacts are not automatically regenerated. Running a repository state refresh updates the summaries to reflect the latest changes.

What steps are needed to check repository status after a Harness Forge refresh?▼

To check repository status after a Harness Forge refresh, optionally run the hforge status command with the --root and --json flags. This verifies the updated runtime state and reports any remaining prerequisites.

Can I refresh runtime state in an uninitialized Harness Forge repository?▼

You cannot fully refresh runtime state in an uninitialized Harness Forge repository. The refresh workflow detects missing initialization and explicitly recommends running the hforge-init process to bootstrap the required artifacts first.

When should I regenerate Harness Forge repo-intelligence artifacts?▼

You should regenerate Harness Forge repo-intelligence artifacts whenever install changes, content updates, or stale artifacts occur. Refreshing the runtime state ensures summaries accurately reflect the current repository configuration and content.

Does the Harness Forge refresh workflow provide post-refresh status checks?▼

The Harness Forge refresh workflow does provide optional post-refresh status checks. By running the hforge status command after refresh, you can verify the updated runtime state and identify any required next actions.

Related Skills

Explore More Software Engineering Skills→
ldilovldilov
3

hforge-analyze

Analyze repository health and risks using Harness Forge runtime artifacts.

Community
Intermediate
ldilovldilov
3

hforge-init

Bootstrap Harness Forge runtime surfaces in a repository.

Community
Advanced
antinomyhqantinomyhq
7.5k

create-command

Scaffold Forge command files with YAML frontmatter in .forge/commands.

Official
Basic
igamenovoerigamenovoer
18

dev-launch-file-browser

Launch and verify the in-repo Filestash file browser via wrapper scripts.

Community
Intermediate