Inspect GitHub pull requests, read review conversations, and investigate failed automated checks with dedicated scripts. Get consolidated status reports, unresolved discussion threads, and failing job or step logs, with full logs saved for further inspection.
中文简介正在准备中。当前显示英语简介。
Use for 1) inspecting PR state, 2) reading review threads, or 3) debugging CI failures. Otherwise use the gh CLI.
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use these scripts only for the three flows listed below. Otherwise use raw
gh. Scripts run TypeScript with Bun and have no dependencies.
| script | use for |
|---|---|
bun run scripts/pr-snapshot.ts [pr] [-R o/r] | full PR state in one call: meta, mergeability, checks, files, reviews, comments, thread counts. Use instead of hand-assembling pr view --json field sets or chaining view/checks/comments calls. |
bun run scripts/pr-threads.ts [pr] [-R o/r] [--all] [--author X] [--since ISO] | the full review conversation: review bodies, issue comments, and unresolved inline threads (resolution state porcelain gh cannot get). Resolved/outdated threads are hidden by default, counted in the header; --all includes them. Read-only: never reply to or resolve threads unless explicitly told to. |
bun run scripts/ci-failures.ts [run-id] [--pr N] [--list] [-R o/r] | failing checks → failing jobs/steps → log snippet each; full logs saved to files (paths printed); rg those instead of re-fetching. --list [--workflow W] [-L n] shows recent runs with conclusions; use it to find the failing run id instead of gh run list --json field sets. |
Rule of thumb: pr-snapshot answers "what's the state of this PR", pr-threads answers "what did reviewers write". Neither replaces the other.
All scripts: --json for structured output, --help for usage (includes the
--json shape). Omit the PR number to use the current branch's PR. Default
output is sized for context; pass --full only when a truncation marker
([…+N chars]) hides something you need. They exit 0 when the report
succeeds even if CI is red or threads are unresolved.
head: SIGPIPE can kill gh mid-write (spurious nonzero
exit, shell-dependent) or silently truncate large output.
Redirect to a file and read that, or trim with --jq '.[0:20]'.gh pr diff has no --stat and no positive pathspec (--name-only and
-e/--exclude globs exist in gh ≥ 2.95). Per-file stats:
gh api 'repos/{owner}/{repo}/pulls/N/files' --jq '.[]|[.filename,.additions,.deletions]|@tsv'
Full diff: gh pr diff N > "$TMPDIR/pr.diff" once, then rg/sed the file.gh pr checks exits 1 = failing, 8 = pending by design; append || true, read the table.gh api 'repos/{owner}/{repo}/contents/PATH?ref=SHA' -H 'Accept: application/vnd.github.raw'gh api fills {owner}/{repo} from the cwd repo (GH_REPO=o/r overrides).
Quote any api path containing ? (zsh globs it), or use -X GET -F per_page=100
(any -f/-F silently flips the request to POST without -X GET).--paginate on any list endpoint (/comments, /files, /reviews); --jq
already runs per page; don't add --slurp.--body-file file.md or a quoted heredoc. Never inline
--body "..." containing backticks.statusCheckRollup (pr view); steps
live under gh run view N --json jobs; gh search prs fields ≠ gh pr view fields.-C; pass -R owner/repo to every command, or cd first.gh api 'repos/{owner}/{repo}/rulesets' on modern repos;
/branches/main/protection 404s unless classic protection is on AND you have
admin ("Branch not protected" or plain "Not Found" both mean check rulesets;
neither is a path error).gh api 'repos/{owner}/{repo}/compare/BASE...HEAD' --jq '{ahead_by,behind_by}'jq -f prog.jq; inline
zsh quoting breaks.gh run watch ID and
gh pr checks N --watch --fail-fast exist; let the harness background them.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Automate website navigation, form entry, and clicks through a browser command line tool. Extract page text, capture screenshots, and compare page states to check interactions or test web app behavior across screen sizes.
中文简介正在准备中。当前显示英语简介。
Rewrite dense or ambiguous English into short, direct sentences using principles from ASD-STE100, a standard for clear technical English. It preserves facts and conditions, identifies writing issues, and shows the original and revised text side by side.
中文简介正在准备中。当前显示英语简介。
Update release base versions for supported packages, keep matching version fields in sync, and verify generated versions. The workflow covers committing and pushing the changes, with guidance for release steps after merging.
中文简介正在准备中。当前显示英语简介。
Compare function call structures across Git commits, branches, or working files to support code review. Display call trees and trace paths from an entry function to a target function, with support for 22 languages.
中文简介正在准备中。当前显示英语简介。
Automate browser tasks from the terminal using the chrome-devtools-mcp CLI. Inspect page elements, click and fill forms, navigate tabs, capture screenshots, and investigate network requests, console messages, performance, and memory through shell commands.
中文简介正在准备中。当前显示英语简介。
Review the changes made during a session and organize them into focused Git commits. The skill groups related files, writes messages explaining why changes were made, and stages specific files while excluding unrelated material.
中文简介正在准备中。当前显示英语简介。