MMGA – Make Merging Great Again
We made a hyper-optimized workflow using codex skills to make PR reviewing and merging super easy.
Core trick
Chains Codex skills that summarize a PR, evaluate it, plan fixes, then rebase, run the gate, and merge.
Tags
Description
We made a hyper-optimized workflow using codex skills to make PR reviewing and merging super easy.
We demonstrate its usefulness by actually merging open PRs on the OpenClaw repo.
This is how it happens step by step, given a PR link:
• r1 — Summarize PR: what changed, why, key files, how it works, unresolved comments
• r2 — Evaluate implementation: simplicity, overengineering, propose alternatives
• r3 — Identify risks + blockers, make decisions, output final plan
• r4 — Implement the plan, add missing tests (no changelog, no test run)
• land-pr — Rebase onto main, changelog, run gate, verify mergeable, merge
README excerpt
# useful-codex-skills A small collection of Codex skills for goals, planning, execution, and code understanding. ## Included skills Planning / execution chain - `grill-me`: Pressure-test a plan or design through a focused decision-tree interview. - `grillcraft`: Compile a completed grilling session into `decision.md`, an improved ExecPlan, and a Goalcraft execution goal. - `execplan-create`: Turn a decided refactor, PRD, RFC, or detailed brief into an ExecPlan inside a work-item directory. - `execplan-improve`: Read an existing ExecPlan, analyze the referenced code paths, and rewrite the plan with concrete, code-grounded improvements. - `implement-execplan`: Execute a work-item ExecPlan or legacy singleton plan while tracking implementation state explicitly. - `review-recent-work`: Review the latest implemented work item or completed ExecPlan, fix obvious issues, and record the result. Goal support - `goalcraft`: Turn a rough draft, vague ambition, or messy task brief into an evidence-checked Codex `/goal` objective. Strategic review - `reorient-myself`: Audit a Codex task from first principles and produce one paste-ready prompt to get it back on track. Code understanding - `explain-code-change`: Investigate a diff, commit, branch, or pull request and publish a verified, learning-oriented explanation to the user's connected Notion workspace. ## How to use Each skill lives in its own folder and is documented in its `SKILL.md`. Skills that declare MCP dependencies, suc