kookr-post-pushlisted

# Post-Push Use this immediately after pushing a branch that has a PR, and again after any follow-up push. This skill does not create a parallel workflow. It is the repo-local reminder to keep driving the existing PR workflow until the branch is actually in a good state. ## What This Skill Composes - `[[kookr-pr-lifecycle]]` for PR creation, checklist updates, and CI monitoring - `[[pr-review-triage]]` for comment triage, fixes, and thread resolution This skill fills the gap between "push succeeded" and "the PR is actually ready." ## Workflow ### 1. Find the current PR If the branch already has a PR: ```bash gh pr view --json number,url,mergeable,mergeStateStatus,reviewDecision ``` If the PR does not exist yet, create or update it via [[kookr-pr-lifecycle]] after `[[kookr-pre-push]]` has completed. **Listing PRs for the post-merge rebase scan:** use `gh prs` (alias: `pr list --limit 200`) or pass `--limit 200` explicitly — the bare `gh pr list` default of 30 silently truncates and misses PRs in busy repos. Set the alias once with `gh alias set prs 'pr list --limit 200'` (older gh versions without `--clobber`: `gh alias delete prs 2>/dev/null; gh alias set prs 'pr list --limit 200'`). ### 2. Check mergeability first Read `mergeable` / `mergeStateStatus` right away. - If GitHub reports merge conflicts or the branch is behind the base branch in a way that needs action, fix that branch state before calling the task done. - After resolving conflicts locally, push agai