Post-push CI verification and fix workflow. Use when: (1) user says "pr-post", "check ci", "check actions", "fix ci", or "are checks passing", (2) after pushing code to a PR branch, (3) when the user wants to verify GitHub Actions status and fix any failures.
76
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Check GitHub Actions on the current PR, diagnose failures, and fix them.
Find the current PR:
gh pr view --json number,url,titleWait for all checks to finish, then check CI status:
gh pr checks <pr-number> --watch --fail-fastThis blocks until all checks complete and exits non-zero if any fail.
If all checks pass, report success and stop.
If any checks fail, identify the latest run for the HEAD commit and get failed job logs:
# List runs for the HEAD commit to find the correct run ID
gh run list --commit $(git rev-parse HEAD) --json databaseId,status,conclusion,name --limit 5
# Then get failed logs from the correct run
gh run view <run-id> --job <job-id> --log-failedIMPORTANT: Never reuse a run ID from a previous step or an earlier push — always derive it from the HEAD commit or the failing check's link URL. Multiple workflow runs may exist; pick the one that matches the failing check name.
Diagnose the failure from logs. Common causes in this repo:
Fix the issue in code, commit with fix: <description>, push.
Re-check CI status. Repeat until all checks pass or the issue needs user input.
d58ca85
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.