resolve-issue-dashboardlisted

Open a live, read-only dashboard that visualises resolve-issue runs across all your repos — each run's pipeline step, what each component skill and subagent is doing, the running metrics, and the gate it is paused at — by tailing the Claude Code transcripts and each repo's .claude/resolve/<ticket>/state.md. One global dashboard lists every run in a left panel; pick one to watch. Use whenever someone wants to see / watch / visualise the progress of an issue-to-PR run, says "open the pipeline dashboard", "show resolve progress", "watch the resolve-issue run", "visualise what the agents are doing", or "/resolve-issue-dashboard". Do NOT trigger to RUN the pipeline — that is resolve-issue — nor for any single stage (route those to the component skill: review-issue-fact, review-plan-risk, review-code-risk, test-authoring, open-pr, resolve-pr-comments). This skill only observes; it never drives the pipeline, answers a gate, or edits anything.
softwareone-platform/issue-to-pr · ★ 1 · AI & Automation · score 67

Install: claude install-skill softwareone-platform/issue-to-pr

# Resolve issue dashboard Open a small local dashboard that visualises `resolve-issue` runs as they happen. **One global dashboard** discovers every run across your repos — by reading the files Claude Code already writes (the session transcripts under `~/.claude/projects/` and each repo's `.claude/resolve/<ticket>/state.md`, plus the run's append-only `timings.md`) — and lists them in a left panel; pick one to watch its pipeline step, per-subagent activity, running metrics, and any gate it is paused at. It is a **read-only observer**: it never writes to a transcript or to `.claude/resolve/`, never answers a gate, and never edits code. Gates are still answered in the Claude Code terminal; the dashboard only shows that one is waiting. Because it is global, launch it **once** (from any repo) and reuse it — running `resolve-issue` in several repos does not need several dashboards. Start it any time; runs appear, switch, and can be inspected after they finish or pause. ## Locate the server The dashboard is served by a stdlib-only Python script bundled with this skill. Resolve the skill directory once via bash injection at load time: !`echo "${CLAUDE_SKILL_DIR}"` Call that `SKILL_DIR`. The server is `SKILL_DIR/scripts/serve_progress.py` and it serves `SKILL_DIR/assets/index.html`. If the line above did not expand to a real absolute path (it still shows a literal `${CLAUDE_SKILL_DIR}`), resolve it at runtime — run `echo "$CLAUDE_SKILL_DIR"` with the Bash tool; if it is empty,