check-prlisted

# Check PR Analyze a pull request for review comments, status checks, and description completeness, then help address any issues found. ## Inputs - **PR number** (optional): If not provided, detect the PR for the current branch. ## Instructions ### 1. Identify the PR If a PR number was provided, use it. Otherwise, detect it: ```bash gh pr view --json number -q .number ``` ### 2. Fetch PR details ```bash gh pr view <PR_NUMBER> --json title,body,state,reviews,comments,headRefName,statusCheckRollup gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments ``` ### 3. Wait for pending checks Before analyzing, ensure all status checks have completed. If any checks are `PENDING` or `IN_PROGRESS`, poll every 30 seconds until all checks reach a terminal state (success or failure). This ensures that review bot comments (Greptile, linters, etc.) are available before analysis. ### 4. Analyze the PR Once all checks are complete, evaluate these areas: #### A. Status Checks - Are all CI checks passing? - If any are failing, identify which ones and the failure reason. #### B. PR Description - Is the description complete and follows team conventions? - Are all required sections filled in? - Are there TODOs or placeholders that need updating? #### C. Review Comments - Inline code review comments that need addressing - Look for bot review comments (e.g. from `greptile-apps[bot]`, linters, etc.) - Human reviewer comments #### D. General Comments - Discussion comments on the PR