From forge
Show Forge project state and harness metrics. Triggers: "forge info", "where are we?", "show progress", "forge metrics", "measure Forge".
npx claudepluginhub cjy5507/forge --plugin forgeThis skill uses the workspace's default tool permissions.
<Purpose>
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
<Use_When>
Load .forge/state.json. If missing → "No active Forge project. Use forge to start one."
Also load if they exist:
.forge/runtime.json — lanes, blockers, ownership, harness stats.forge/holes/ — issue counts by severityforge/*Build mode (N/9):
| Phase | Range |
|---|---|
| 0–1 | 0–25% |
| 2 | 25–40% |
| 3 | 40–55% |
| 4 | 55–70% |
| 5–6 | 70–85% |
| 7 | 85–95% |
| 8 | 95–100% |
Repair mode (N/7):
| Phase | Range |
|---|---|
| 0–1 | 0–25% |
| 2 | 25–50% |
| 3 | 50–70% |
| 4–5 | 70–90% |
| 6 | 90–100% |
Within Phase 4, refine by lane completion ratio (done lanes / total lanes).
Forge: {{project_name}} ({{build|repair}})
Phase {{N}}/{{max}} — {{phase_name}}
{{progress_bar}} {{X}}%
Next action: {{next_action_summary}}
{{actionable_summary}}
Lanes: {{done}}/{{total}} done{{if blocked}}, {{blocked}} blocked{{/if}}
Issues: {{blocker}} blocker, {{major}} major, {{minor}} minor
Tag: {{latest_tag}}
Harness: tier={{tier}} sessions={{N}} agents={{N}} failures={{N}} stops={{N}}
Use runtime.next_action.summary when present. That is the canonical next-step line.
Then derive the supporting summary below. Pick the FIRST that applies:
| Priority | Condition | Output format |
|---|---|---|
| 1 | Customer blocker exists | "Waiting on you: {{what's needed}}" |
| 2 | Internal blocker exists | "Blocked: {{description}} (owner: {{role}})" |
| 3 | Delivery ready for review | "Ready for review — run forge deliver to finalize" |
| 4 | Lanes in progress | "Active: {{lane names}}. Next: {{recommended action}}" |
| 5 | Default | "Phase {{name}} in progress" |
When lanes exist, append ownership context after the lane count:
Lanes: 2/5 done, 1 blocked
auth-api (developer, in_progress) — last: "API routes done, testing auth middleware"
db-schema (cto, blocked) — waiting on contract review
Only show lane detail for non-done lanes. Keep it to one line per lane.
When the user asks "forge info --verbose", "detail", or "detailed":
Default is always the compact view.
<Progressive_Disclosure>
skills/ignite/references/harness-ab-eval.md when a structured with/without comparison is needed.
</Progressive_Disclosure><Tool_Usage>
node scripts/forge-status.mjs (--json or --verbose as needed)
</Tool_Usage>