메뉴
Use when safely merge GitHub pull requests that are ready
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when you need an evidence-first, read-only inventory of every automation in this repo (GitHub Actions, Claude Code hooks/settings, MCP servers, composer scripts, the bundled CLI installer, the skills catalog, scheduler/cron) before changing any of them, classifying each as live, broken, or redundant and recommending keep/merge/cut/fix.
Use when choosing how to run Claude Code autonomously on this project — from a single sequential pipeline to multi-agent DAG orchestration. A reference catalog of loop patterns anchored to this repo's real tooling (resolve-issue, autoresolve-oldest-github-issue, code-review-github, process-code-review, merge-github-pr, /loop), with composer build / composer skill-check as the quality gate between iterations.
Use when a goal is vague speed ("make it faster", "reduce p95", "cut query time") and you need a bounded, measured loop that promotes only verified, correctness-preserving wins instead of guessed micro-tweaks.
Use when measuring performance baselines or detecting regressions before and after a change in a Laravel app — page Core Web Vitals, API latency percentiles, build/test velocity, and DB query timing, stored as git-tracked baselines for team comparison.
Use when a single objective is too large for one pull request and must span multiple sessions or PRs. Turns the objective into a sequenced construction plan of 3-12 one-PR steps, each with a cold-start context brief, dependency edges, and exit criteria, then reviews it adversarially and registers it as Markdown.
Use when refactor PHP classes to improve structure, readability, and maintainability while preserving behavior
SOC 직업 분류 기준
| name | merge-github-pr |
| description | Use when safely merge GitHub pull requests that are ready |
| license | MIT |
| metadata | {"author":"Petr Král (pekral.cz)"} |
Merge pull requests that meet all required conditions.
skills/code-review-github/scripts/load-issue.sh <NUMBER|URL> — the single deterministic entry point. Never call gh pr view, gh pr checks, or gh api /repos/.../pulls/... directly. Read mergeable, mergeStateStatus, reviewDecision, and statusCheckRollup[] off the resulting JSON document.For each PR, derive the verdict from the JSON document loaded in step 1:
mergeable == "MERGEABLE" and mergeStateStatus is not DIRTY or BEHINDstatusCheckRollup[] has a passing state (SUCCESS / NEUTRAL / SKIPPED)reviewDecision == "APPROVED"mergeStateStatus != "BEHIND"If any check fails: