Pr analysis
Use this workflow skill for a deep, read-only PR review covering intent, code quality, regression risk, test gaps, and feedback status; prefer it over check-ci when the request is broader than CI triage.From its SKILL.md
npx -y skills add kaeawc/auto-mobile --skill pr-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.7 KB, as published. Nobody here has run it
PR Analysis
Perform a read-only PR review that covers intent, correctness, regression risk, tests, and existing feedback.
Workflow
- Resolve the PR with
gh pr view <pr> --json ...and capture the head branch, base branch, title, and body. - Gather context with
gh pr diff,gh pr diff --stat,gh pr checks, and all paginated review, inline, and conversation comments plus review verdicts. - Always collect GraphQL review-thread state: unresolved and outdated threads are not
represented reliably by flat comment views. Reuse
github-pr-feedbackfor the collection and the ledger. - Read full changed files from the PR branch and the base branch, not just diff hunks.
- Find related callers, interfaces, and tests in the local codebase.
- If validation is warranted, run the lightest relevant repo validation rather than a blanket heavy build.
- Produce findings first, then open questions, then a short summary.
Repo Rules
- Prefer
ghfor PR metadata and CI data. - Prefer repo validations:
- TypeScript:
bun run lint,bun run build,bun test - Fast checks:
bash scripts/all_fast_validate_checks.sh - Android or iOS only when the PR actually touches those areas
- TypeScript:
- Keep the analysis read-only unless the user explicitly asks for fixes.
- When saving large diffs or logs, put them in
scratch/.
Output Structure
- Findings ordered by severity with
file:linereferences - Open questions or assumptions
- Brief change summary and residual risks