adopt
Bootstrap an existing repo for ForgeDock — triage open issues, apply labels, suggest a starter milestone, and identify first…
<!-- SPDX-FileCopyrightText: Copyright (c) RapierCraft Studios --> <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
> /plugin marketplace add RapierCraftStudios/ForgeDock > /plugin install forgedock@forgedock
How it fires
How this command gets triggered: by you, by Claude, or both.
/phase-5-reportContext preview
What this command does when you run it.
<!-- SPDX-FileCopyrightText: Copyright (c) RapierCraft Studios --> <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
user-invocable: false install: extras
<!-- SPDX-FileCopyrightText: Copyright (c) RapierCraft Studios --> <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
> **Skill names**: `{FORGE_SKILL_PREFIX}` is `forgedock:` (plugin install) or empty (`install.sh`), resolved once per run by `commands/work-on.md` § Skill Name Resolution. If the skill is not found under either name, STOP and report "skill not found" — never run the phase inline.
Create a detailed health report as a GitHub issue in the Forge repo, routed through the `/issue` programmatic create-hook (#2085) instead of a raw `gh issue create`. Because `/issue`'s programmatic mode resolves `GH_REPO` from `forge.yaml → project.owner/repo` (via `$FORGE_CONFIG`, default `forge.yaml`) with no explicit `-R` override, and `$FORGE_REPO` may differ from the analyzed project's own repo (`forge.yaml → project.forge_repo`, see Config Resolution), point `$FORGE_CONFIG` at a synthesized minimal config for the duration of the call so the create-hook targets the Forge repo, not the analyzed repo:
FORGE_ISSUE_HOOK_CONFIG=$(mktemp)
cat > "$FORGE_ISSUE_HOOK_CONFIG" <<HOOKCFG_EOF
project:
owner: "${FORGE_REPO%%/*}"
repo: "${FORGE_REPO##*/}"
paths:
root: "$FORGE_HOME"
HOOKCFG_EOF
HEALTH_BODY_FILE=$(mktemp)
cat > "$HEALTH_BODY_FILE" <<'EOF'
## Pipeline Health Report
**Project**: $REPO
**Period**: $SINCE → $(date +%Y-%m-%dT%H:%M:%SZ)
**Health Score**: [SCORE]/100 ([CATEGORY]) $SCORE_TREND
## Metrics
### Pre-Merge Quality
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Build pass rate (staging→main) | ?% | 95%+ | ✅/⚠️/❌ |
| Review findings per PR | ? | < 0.5 | ✅/⚠️/❌ |
| Review noise share (dropped, pre-existing or demoted / candidate findings; from 2E.5) | ?% | < 20% | ✅/⚠️/❌ |
| Manual fix-up rate | ?% | < 15% | ✅/⚠️/❌ |
| False positive rate | ?% | < 10% | ✅/⚠️/❌ |
| Pipeline self-correction rate | ?% | < 15% | ✅/⚠️/❌ |
### Post-Deploy Quality
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Post-deploy failure rate | ?% | < 5% | ✅/⚠️/❌ |
| Review escape rate (REVIEW_FALSE_NEG) | ?% | < 2% | ✅/⚠️/❌ |
| Mean time to detect | ? days | < 7 days | ✅/⚠️/❌ |
| Audit findings (total in window) | ? | — | ℹ️ |
| — by failure point | see breakdown | — | ℹ️ |
### Pipeline Health Signals
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Issue quality score | ?/100 | > 80 | ✅/⚠️/❌ |
| — Investigation invalidation rate | ?% | < 15% | ✅/⚠️/❌ |
| — ISSUE_SPEC audit findings | ? | 0 | ✅/⚠️/❌ |
| — Re-investigation rate | ? | 0 | ✅/⚠️/❌ |
| — Issue structure compliance | ?% | > 80% | ✅/⚠️/❌ |
| Investigation accuracy (trajectory) | ?% | > 85% | ✅/⚠️/❌ |
| Orchestration efficiency score | ?/100 | > 70 | ✅/⚠️/❌ |
| — Avg agent idle% | ?% | < 30% | ✅/⚠️/❌ |
| — Avg resume cycles per agent | ? | < 1 | ✅/⚠️/❌ |
| — Clean agent rate | ?% | > 60% | ✅/⚠️/❌ |
| — Batch stall rate | ?% (?/? issues) | < 10% | ✅/⚠️/❌ |
| — Escalated to needs-human | ? issues | 0 | ✅/⚠️/❌ |
| Original work ratio | ?% | > 70% | ✅/⚠️/❌ |
| Milestone merge success | ?% | 80%+ | ✅/⚠️/❌ |
| Issue close velocity | ? days | < 2 days | ✅/⚠️/❌ |
| Transcript health score (Phase 2N/2Q) | ?/100 $(_trend $TRANSCRIPT_HEALTH_SCORE $PRIOR_TRANSCRIPT_SCORE) | > 70 | ✅/⚠️/❌/ℹ️ |
| — Session flow flag | [✅ Healthy / ⚠️ flag / ℹ️ unavailable] | — | ℹ️ |
| — Aggregated session metrics (Phase 2Q) | [✅ Available / ℹ️ unavailable] | — | ℹ️ |
| Avg cost per issue (FORGE:DECISION_RECORD) | $? / ℹ️ unavailable | — | ℹ️ |
## Trajectory Analytics
_From Phase 2I — FORGE:TRAJECTORY comments on [N] closed issues in window_
| Metric | Value |
|--------|-------|
| Issues with trajectory data | ? / ? closed |
| Investigation accuracy | ?% (CONFIRMED: ?, PARTIAL: ?, INVALID: ?) |
| Task type distribution | Bug Fix: ?, Feature: ?, Refactor: ?, Maintenance: ? |
| Anomalies flagged | ? issues |
| Notable anomalies | [list top 3 or "None"] |
_If no trajectory data available in window: "No FORGE:TRAJECTORY comments found — pipeline may be running pre-trajectory version or window is too narrow."_
## Orchestration Efficiency
_From Phase 2K — persisted FORGE:AUDIT-AGENTS summaries ([N] sessions, [M] agents total) + FORGE:STALL_DETECTED annotations_
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Avg agent idle% | ?% | < 30% | ✅/⚠️/❌ |
| Avg resume cycles per agent | ? | < 1 | ✅/⚠️/❌ |
| Clean agent rate | ?% | > 60% | ✅/⚠️/❌ |
| Batch stall rate | ?% (?/? issues) | < 10% | ✅/⚠️/❌ |
| Escalated to needs-human | ? issues | 0 | ✅/⚠️/❌ |
**Top stall boundaries** (phase transitions causing the most stalls):
| Boundary | Occurrences |
|----------|-------------|
| [boundary_1] | [N] |
| [boundary_2] | [N] |
| [boundary_3] | [N] |
_If no FORGE:AUDIT-AGENTS data available: "No persisted audit-agents summaries found in window. Run \`audit-agents --persist\` after orchestration runs to enable this metric. Proxy: [N] issues had resume/stall anomalies in trajectory data."_
_Batch stall rate: sourced from \`FORGE:STALL_DETECTED\` comments (requires \`/orchestrate\` Step 4B.5 to be active). N/A if stall detector is not deployed._
## Transcript Flow Metrics
_From Phase 2N — JSONL transcript analytics ([N] pipeline sessions, [M] subagent sessions in window)_
| Metric | Value | Signal |
|--------|-------|--------|
| Pipeline sessions parsed | ? parent, ? subagent | ℹ️ |
| Total turns with timing | ? | ℹ️ |
| Avg turn duration | ?s | ℹ️ |
| Max turn duration | ?s | ℹ️ |
| Stall turns (>120s) | ? (?%) | ✅/⚠️ |
| Rate-limit indicator turns (60–120s) | ? | ℹ️ |
| Context compaction events | ? | ✅/⚠️ |
| Session flow flag | [✅ Healthy / ⚠️ High stall rate / ⚠️ Frequent compaction] | — |
**Top tools by call frequency**:
| Tool | Calls |
|------|-------|
| [tool_1] | [N] |
| [tool_2] | [N] |
| [tool_3] | [N] |
_IfForgeDock — autonomous AI dev pipeline for Claude Code. GitHub as agent memory: issue in, PR out.
Bootstrap an existing repo for ForgeDock — triage open issues, apply labels, suggest a starter milestone, and identify first…
Pull production analytics from GSC, Bing Webmaster, Clarity, Umami, Cloudflare, Stripe, and GA4 — generate insights and create…
Audit agent outputs from an orchestration run — timeline analysis, stall detection, active vs idle time breakdown
Trace a production issue or pipeline failure end-to-end through GitHub artifacts, then file a detailed improvement issue to the…
Autonomous deploy loop — runs until zero open issues remain. Detects pipeline state and resumes from any position. Fully…
Guided idea-to-backlog setup for a brand-new project — interview, defaults, doubts, spike doc, validated orchestrate-ready backlog