メニュー
Use when summarizing GitHub PR checks, pending/failing CI status, check links, and suggested gh run commands without downloading noisy logs by default.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | github-pr-checks-diagnostics |
| description | Use when summarizing GitHub PR checks, pending/failing CI status, check links, and suggested gh run commands without downloading noisy logs by default. |
Use when you need a compact status report for PR checks/CI.
Failing or pending checks are data, not a tool failure. The tool exits 0 when it successfully retrieves check status, even if CI is red or pending.
# Build step (one-time or when tools change):
tsc --project $HOME/.agents/skills/github/tools/tsconfig.json
# Then run:
node $HOME/.agents/skills/github/tools/dist/pr-checks-diagnostics.js --repo OWNER/REPO --pr PR_NUMBER
Defaults:
--repo from git origin--pr from current branch via gh pr view/tmp Markdown and JSON artifactsThe summary groups checks by GitHub CLI bucket, usually:
failpendingpassskippingEach check includes name, state, workflow, link, timestamps, and best-effort suggested commands. For GitHub Actions links, suggestions may include:
gh run view RUN_ID -R OWNER/REPO --log-failed
gh run view RUN_ID -R OWNER/REPO --web
If no run ID can be extracted, use the raw link in the report directly rather than copy/pasting generated shell commands.
gh run view ... --log-failed for targeted logs.Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.
Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.
Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.