ワンクリックで
pr-health
Check PR health status (conflicts, CI, approval) and get actionable next steps
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Check PR health status (conflicts, CI, approval) and get actionable next steps
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
BuildKite CI/CD pipeline configuration, YAML syntax, dynamic pipelines, and agent management When user works with BuildKite, mentions CI pipelines, .buildkite/ directory, buildkite-agent commands, pipeline YAML, build steps, BuildKite API, or asks about CI configuration, pipeline generation, step dependencies, retry configuration, agent queues, or Kubernetes CI agents
Monitor a PR through reviews and merge conflicts until ready for human review. Use when user says "monitor PR", "watch PR", or wants automated PR workflow. Creates PR if needed, then monitors review comments and merge conflicts. Note: this monorepo's CI runs on Buildkite (`buildkite/monorepo/pr` + `ci/merge-conflict`) per PR — watch it via `bk build view` or the Buildkite web UI, not `gh run`.
Use when asking about generating Helm types, HelmValuesForChart, TypeScript interfaces from Helm charts, or the helm-types CLI.
Talos Linux cluster administration using talosctl When user mentions Talos, talosctl, or Talos cluster operations
Use when asking about version management, Renovate annotations, versions.ts patterns, or pinning image/chart versions.
Git version control best practices, advanced operations, and modern features When user works with git, mentions git commands, branching, rebasing, merging, or git troubleshooting
| name | pr-health |
| description | Check PR health status (conflicts, CI, approval) and get actionable next steps |
| user-invocable | true |
| allowed-tools | ["Bash","Read"] |
Branch & PR management in
shepherdjerred/monorepouses git-spice — every PR is a stacked PR. Load thegit-spice-helperskill first for creating/updating/restacking PRs; this skill just reports health. A single PR is a stack of one.
Check the health of a pull request including merge conflicts, CI status, and approval status.
Note: this monorepo's CI runs on Buildkite (
buildkite/monorepo/pr+ci/merge-conflict) per PR in the stack — the CI section reports those checks.toolkit pr logstargets GitHub Actions run IDs, so use Buildkite tooling (bk build view) or the Buildkite web UI for logs on this repo; thetoolkit pr logscommands below still apply to other repos.
Review gate: a red
buildkite/monorepo/pris often the blocking code-review gate (review-gatestep) waiting on the active provider (Codex by default, viaREVIEW_PROVIDER) to review the head and on its threads to be resolved. Re-trigger with@codex review, and probe what the provider did withGH_TOKEN=$(gh auth token) bun scripts/probe-review-signal.ts <pr>. See thebuildkite-helperskill → "Review gate" andpackages/temporal/CLAUDE.md.
# Check PR for current branch
toolkit pr health
# Check specific PR
toolkit pr health 123
# Output as JSON
toolkit pr health --json
# Specify repository
toolkit pr health --repo owner/repo
# Get all logs for a run
toolkit pr logs <run-id>
# Get only failed job logs
toolkit pr logs <run-id> --failed-only
# Get logs for specific job
toolkit pr logs <run-id> --job "build"
# Find PR for current branch
toolkit pr detect
# Output as JSON
toolkit pr detect --json
The health command outputs a structured report:
## PR Health Report: #123
**URL:** https://github.com/owner/repo/pull/123
### Status: UNHEALTHY (2 issues)
### Merge Conflicts: UNHEALTHY
- Branch has merge conflicts with base
- Conflicting file: src/lib/parser.ts
To investigate:
\`\`\`bash
git fetch origin main && git merge origin/main
\`\`\`
### CI Status: FAILED
- Job "test" - FAILED
- Run ID: 12345678
To investigate:
\`\`\`bash
toolkit pr logs 12345678 --failed-only
\`\`\`
### Approval: APPROVED
- claude-code-review[bot]: APPROVED
### Next Steps
1. Resolve merge conflicts
2. Fix CI failures
Create a PR first or specify a PR number:
gh pr create
# or
toolkit pr health 123
The workflow run may not have generated logs yet. Wait for the run to complete.
Ensure you have fetched the latest from origin:
git fetch origin main