메뉴
Use when checking whether GitHub Actions CI has run or passed on a pull request via the GitHub MCP tools (`mcp__github__pull_request_read`) — before claiming CI is green, red, or hasn't run yet.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Interpret lenslab analyse JSON, relay only CLI-prescribed capture fixes, and keep the Rust CLI as the only measurement engine. Use when a user wants to assess a lens copy from DNG/TIFF captures, understand copy_assessment support, or get reshoot guidance.
Interpret lenslab analyse JSON and coach lens-copy capture reshoots using the shared lenslab skill core.
Use before opening, updating, or merging a lenslab PR, especially after decode, core, dependency, binary-size, roadmap, or CLI-output changes. Checks roadmap freshness, crate boundaries, release-size impact, and PR verification evidence.
Use after a larger piece of work or specialised targeted bugfix, before merge, to decide what should be compounded as a repo-local skill, a docs/solutions institutional learning, a rule update, or nothing. Start by showing candidates, then produce only the artefacts that earn their place.
Use when a rustup toolchain install is broken — `cargo`/`rustc` missing or failing to load (e.g. `librustc_driver-*` dylib/so not found), or `rustup toolchain install` reports "toolchain is already up to date" yet rustc errors. Repairs an interrupted toolchain install (common after a setup-script or container interruption).
| name | github-pr-ci-status |
| description | Use when checking whether GitHub Actions CI has run or passed on a pull request via the GitHub MCP tools (`mcp__github__pull_request_read`) — before claiming CI is green, red, or hasn't run yet. |
get_status vs get_check_runsmcp__github__pull_request_read with method: "get_status" returns "total_count": 0 on a PR that
has GitHub Actions workflows configured and has visibly run them (confirmed separately via
mcp__github__actions_list or the Actions UI). This reads as "no CI has run against this commit,"
and is wrong.
get_status calls GitHub's legacy Combined Commit Status API (GET /commits/{sha}/status) — the
API older third-party CI integrations (Travis, CircleCI, pre-Checks-API Jenkins) use to post a
status directly onto a commit. GitHub Actions does not use this API. It reports through the
separate Checks API instead. A repository whose only CI is GitHub Actions will always return
total_count: 0 from get_status, regardless of whether any workflow has run, is running, or
failed — the field is simply not populated by that integration path.
Use method: "get_check_runs" instead — it calls the Checks API and returns the actual GitHub
Actions job list (name, status, conclusion) for the PR's head commit. This is the only one of the
two methods that reflects Actions results.
If you need run-level detail (timestamps, the workflow run/job URLs, commit message per run), use
mcp__github__actions_list (method: "list_workflow_runs") instead or in addition.
get_status's zero is not "pending" or "no data yet" in the way a fresh/uncompleted run would show
under get_check_runs (there you'd see "status": "in_progress" or "queued" entries, not an
empty list). A get_status zero tells you nothing about Actions; treat it as answering a different
question ("are there any legacy commit statuses"), not "has CI run."