grlisted

# Greptile Review, Merge, and Deploy Take the current PR from review through verified production deployment. Keep working until Greptile has no actionable findings, every current check is terminal without failures, GitHub reports the PR merged, the merged revision is deployed through the repository's documented production path, and production verification passes. A check being non-required does not make its failure safe to ignore. ## Resolve the PR and base 1. Read repository instructions and inspect the worktree before changing anything. Preserve unrelated user changes. 2. Resolve the current PR with `gh pr view --json number,url,headRefName,baseRefName,mergeStateStatus,statusCheckRollup`. 3. Fetch the PR base and head from `origin`. 4. Review against `origin/<baseRefName>`, never a possibly stale local base branch. Confirm the diff with `git diff --stat origin/<baseRefName>...HEAD`. 5. If the branch is behind its remote base, rebase or merge according to repository convention before the final review. Use guarded force-pushes (`--force-with-lease`) after rebasing. ## Run Greptile 1. Confirm the CLI is available and authenticated with `greptile --version` and `greptile whoami`. 2. Inspect repository review rules with `greptile config`. 3. Run a fresh machine-readable review: ```bash greptile review -b origin/<baseRefName> --json --instructions "Review rigorously for correctness, security, lifecycle races, data loss, performance regressions, error handling, and mis