pr-readiness-check

To check for missing tests and JSDoc before opening a pull request, run an automated diff analysis on your current branch to flag readiness gaps and guideline violations across changed files.

PR readiness analysis scans your branch diff to identify pre-merge gaps by enforcing checks against project guidelines, flagging missing tests, and detecting absent JSDoc in changed files.

Automate code reviews by running a diff analysis check on your current branch, which enforces project guidelines and surfaces documentation or testing gaps across changed files before submission.

Yes, you can use a diff analysis check to audit your branch for absent JSDoc, generating a readiness report that highlights missing documentation and guideline violations prior to merging.

Automated PR readiness checks require access to the diff output and are limited to flagging missing tests, absent JSDoc, and guideline violations, meaning they cannot evaluate complex architectural logic.

Yes, PR readiness checking works for pre-merge quality gates by scanning the current branch diff to surface missing tests and documentation issues, ensuring code meets typical testing standards before review.