---
name: "hforge-analyze"
description: "Analyze the current repository using Harness Forge runtime surfaces, refresh stale findings when needed, summarize repo shape and risks, and promote architecture-significant findings into durable notes or decision candidates."
compatibility: "Works best in repositories already initialized with Harness Forge, but may bootstrap first if needed."
metadata:
author: "harness-forge"
source: "skills/hforge-analyze/SKILL.md"
User Input
$ARGUMENTS
You must consider the user input before proceeding.
Goal
Use Harness Forge as the primary repo-analysis system instead of re-deriving the repository state from scratch.
Execution
Treat the text after /hforge-analyze as the focus area or analysis lens.
Inspect .hforge/agent-manifest.json, .hforge/runtime/index.json, and .hforge/runtime/repo/ first when present.
Run hforge status --root . --json.
If runtime artifacts are missing or stale, run hforge refresh --root . --json.
Run hforge review --root . --json when health, decision coverage, or stale task state matters.
Summarize:
repo shape
dominant languages and frameworks
risks and validation gaps
recommended next actions
When the analysis reveals architecture-significant changes, promote them into an ASR or ADR under .hforge/runtime/decisions/.
Keep product code unchanged unless the user explicitly asks for edits.
1---2name: hforge-analyze-23description: ---4---5---6name: "hforge-analyze"7description: "Analyze the current repository using Harness Forge runtime surfaces, refresh stale findings when needed, summarize repo shape and risks, and promote architecture-significant findings into durable notes or decision candidates."8compatibility: "Works best in repositories already initialized with Harness Forge, but may bootstrap first if needed."9metadata:10 author: "harness-forge"11 source: "skills/hforge-analyze/SKILL.md"12---1314## User Input1516```text17$ARGUMENTS18```1920You must consider the user input before proceeding.2122## Goal2324Use Harness Forge as the primary repo-analysis system instead of re-deriving the repository state from scratch.2526## Execution27281. Treat the text after `/hforge-analyze` as the focus area or analysis lens.292. Inspect `.hforge/agent-manifest.json`, `.hforge/runtime/index.json`, and `.hforge/runtime/repo/` first when present.303. Run `hforge status --root . --json`.314. If runtime artifacts are missing or stale, run `hforge refresh --root . --json`.325. Run `hforge review --root . --json` when health, decision coverage, or stale task state matters.336. Summarize:34 - repo shape35 - dominant languages and frameworks36 - risks and validation gaps37 - recommended next actions387. When the analysis reveals architecture-significant changes, promote them into an ASR or ADR under `.hforge/runtime/decisions/`.398. Keep product code unchanged unless the user explicitly asks for edits.
Run npx skillmds@latest add ldilov/hforge-analyze-2 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