Ask me what skills you need
What are you building?
Tell me what you're working on and I'll find the best agent skills for you.
Check branch changes for common PR readiness issues (missing tests, missing JSDoc, guideline violations). Use when the user asks to verify changes before opening a PR, check code quality, or audit a branch for missing items.
Scan the current branch diff for common issues that could be flagged during PR review. This is a non-blocking check — always report findings as warnings and let the user decide what to act on.
The canonical Definition of Ready For Review lives at docs/readme/ready-for-review.md.
Collect the diff
git diff main...HEAD --name-only
git diff main...HEAD
Check for missing tests
For each new or modified source file with non-trivial logic changes (not just config, docs, or styles), check whether a corresponding test file was added or updated.
Heuristic: a source file Foo.ts(x) should have a matching Foo.test.ts(x) (or Foo.view.test.tsx for components). Warn if:
Check for missing JSDoc
Scan new exported functions, types, and components in the diff. Warn if any lack JSDoc comments.
Check for guideline violations
npx skills add MetaMask/metamask-mobile --skill pr-readiness-checkHow clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
Clear and well structured, with only minor parts that might need a second read.
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
Mostly actionable with clear steps; only a few small gaps remain.