audit
Audit one or more specific pull requests the user names — PR numbers, `#N`, or GitHub URLs (e.g. "/audit 2101", "/audit
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- audit
- metadata
- { "internal": true }
- description
- Audit one or more specific pull requests the user names — PR numbers, `#N`, or GitHub URLs (e.g. "/audit 2101", "/audit
02 资源文件 1
- 参考文档procedure.md15.9 KB
03 SKILL.md 正文
Pull request audit
The user names the PRs — one or many. Audit them one at a time: fix each, push it, and ask the user to merge or close it. The user merges; you never do.
1. Take the list
Accept any mix of 2101, #2101 and PR URLs, separated by spaces, commas or
newlines. Dedupe. A URL for another repository (e.g. alchemy-run/distilled)
is audited with -R <owner>/<repo> on every gh call, in that repository's
checkout (submodules/distilled).
gh pr view <n> --json number,title,author,state,isDraft,mergeable,additions,deletions,changedFiles,updatedAt,isCrossRepository,maintainerCanModify,headRefName,baseRefName,url
Say up front which PRs are already merged, closed or don't exist, and drop
them. Drafts, PRs waiting on the author's answer to an earlier question, and
forks we can't push to (maintainerCanModify: false) stay — the user asked
for them — but say so; on an unpushable fork, fixes go to the author as a
standalone comment or a follow-up PR.
One PR: no table. Go straight to §2 and end with the §7 report.
Several PRs: print a table —
# | PR (link) | Author | Size | Behind main | What it does | Audit notes,
with ✅/❌ against the standards in
procedure.md §3 — and annotate:
- stacks — a PR whose
baseRefNameis another listed PR's branch (base #N ← child #M); the base goes first - overlaps — PRs fixing the same issue or touching the same files; plan a merge order and which ones to close
Keep the user's order otherwise; if they gave none, easiest first (clean
merge, small diff, tests already in the right shape, single concern). Track
status (todo / in progress / ready → merge? / close? / merged /
closed / parked) and re-print the table whenever it changes.
2–7. Audit each PR
Work through the list with the shared per-PR procedure in procedure.md: check out and merge main, review the code, update JSDoc, run the tests, push and rewrite the description, then report and ask. Read it in full before the first PR.
8. Keep the list moving
Follow procedure.md §8, plus:
- On "also audit #N": fetch it as in §1, add it to the table (respecting stacks and overlaps), and finish the current PR first.
- When every listed PR is
merged,closedorparked, print the final table and stop. Don't search for more PRs — that's pr-queue.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
pull-requests
Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.