hforge-analyze

Analyze the current repository using Harness Forge runtime surfaces, refresh stale findings when needed, summarize repo shape and risks, and promote…

Skill by harness-forge

IndexedGPL-3.0★ 6

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/ldilov-hforge-analyze

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/hforge-analyze

What's inside

Skill 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.
License: GPL-3.0
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
Instructions: 28 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

## User Input

```text
$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

1. Treat the text after `/hforge-analyze` as the focus area or analysis lens.
2. Inspect `.hforge/agent-manifest.json`, `.hforge/runtime/index.json`, and `.hforge/runtime/repo/` first when present.
3. Run `hforge status --root . --json`.
4. If runtime artifacts are missing or stale, run `hforge refresh --root . --json`.
5. Run `hforge review --root . --json` when health, decision coverage, or stale task state matters.
6. Summarize:
   - repo shape
   - dominant languages and frameworks
   - risks and validation gaps
   - recommended next actions
7. When the analysis reveals architecture-significant changes, promote them into an ASR or ADR under `.hforge/runtime/decisions/`.
8. Keep product code unchanged unless the user explicitly asks for edits.

From ldilov/harness-forge, GPL-3.0.

Signals

Stars: 6
Forks: 1
Open issues: 0
Last commit (this folder): Mar 28, 2026 (7 months ago)
Last release: Apr 7, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: GPL-3.0
Repository: github.com/ldilov/harness-forge
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from harness-forge

Cite this page

hforge-analyze skill. Agent Mart. https://agentmart.dev/skills/ldilov-hforge-analyze (last updated 2026-10-24)