Menú
View a CI run by ID, URL, PR number, or branch (defaults to current branch)
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | view-run |
| description | View a CI run by ID, URL, PR number, or branch (defaults to current branch) |
| argument-hint | [run-id, run-url, pr-number, or branch] |
| allowed-tools | Bash(gh run *), Bash(gh pr *), Bash(git branch *), mcp__gitea__actions_run_read, mcp__gitea__pull_request_read |
git remote -vgit branch --show-currentCheck the git remotes above to determine the platform:
github.com → use gh CLImcp__gitea__actions_run_readView and summarize a CI workflow run.
No arguments: View the most recent run for the current branch:
gh run list --branch $(git branch --show-current) --limit 1
Then view that run ID.
GitHub Actions URL (e.g. https://github.com/owner/repo/actions/runs/123/job/456?pr=789): Extract the run ID from the URL and view it. Use --repo owner/repo if it differs from the current repo.
Run ID (numeric): View it directly:
gh run view $ID
PR number (e.g. #784 or 784 when contextually a PR): Find the PR's head branch, then get the most recent run for that branch:
gh pr view $PR --json headRefName -q .headRefName
gh run list --branch $BRANCH --limit 1
Branch name: List the most recent run for that branch:
gh run list --branch $BRANCH --limit 1
Once you have the run ID:
gh run view $RUN_ID
If a specific job failed, show its logs:
gh run view $RUN_ID --log-failed
Extract owner/repo from the remote URL.
mcp__gitea__actions_run_read with method list_runs to find recent runs.get_run with the run_id.mcp__gitea__pull_request_read with method get to find the head branch, then list_runs.For failed jobs, use list_run_jobs to find the failed job, then get_job_log_preview for error output.
Summarize concisely: workflow name, status, conclusion, branch, triggering commit/PR, duration, and any failed steps with relevant error output.
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.