codex-issue-waves

Run a batch of GitHub issues through codex exec in isolated git worktrees as parallel autonomous PRs, then manage the review and correction waves until merge. Use when the user gives a list of issue numbers (≥ 2) and asks to "spawn codex" / "dispatch codex" / "have codex work on" / "manage the PRs" / "process feedback" / "get them merged" for those issues, or when the user asks for multi-issue parallel delegation to codex. Not for single-issue wave-driven delegation (use codex-task-waves), single-issue one-shot dispatch (use invoking-codex-exec), or implementation without delegation (use /pr or direct implementation).

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestration skill: clear phased workflow with validation checkpoints and feedback loops, excellent progressive disclosure pointing to real reference/script files. Minor conciseness drag from repeated framing and some actionability reliance on the sibling invoking-codex-exec skill.

Suggestions

Consolidate the repeated 'Claude is PO / codex is worker' and 'status vs content' framing — state it once in the orchestration model and reference it from the review wave and key pitfalls rather than restating.

Inline a one-line canonical codex launch incantation (or a tight snippet from invoking-codex-exec) so the dispatch and reviewer steps are executable without context-switching to the sibling skill.

Dimension	Reasoning	Score
Conciseness	Lean and procedural, assuming Claude's intelligence (no explanation of worktrees/codex), with mechanics delegated to invoking-codex-exec; slightly held back by repeated status-vs-content and PO/worker framing across the orchestration model, review wave, and key pitfalls sections.	4 / 5
Actionability	Concrete copy-paste commands throughout (gh pr view --json ..., git log --oneline, git diff --stat, scripts/wait_for_ci.sh, scripts/merge_and_cleanup.sh), but the actual codex launch mechanics and prompt shape are deferred to invoking-codex-exec and references rather than fully self-contained.	4 / 5
Workflow Clarity	Four phases (dispatch → monitor → review wave → correction wave → merge) are clearly sequenced with explicit validation checkpoints (PR existence check, read-only enforcement, JSON parseability, 'After 3 corrector cycles escalate') and review→correct→re-review feedback loops for this batch operation.	5 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to real bundle files (references/prompt-template.md, common-commands.md, pitfalls.md, scripts/wait_for_ci.sh, merge_and_cleanup.sh); content appropriately split with easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, natural trigger phrases, explicit what/when guidance, and clear disambiguation against sibling skills. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Run a batch of GitHub issues through codex exec in isolated git worktrees as parallel autonomous PRs', 'manage the review and correction waves until merge' — with comprehensive coverage of the workflow.	5 / 5
Completeness	Explicitly answers both 'what' (run issues through codex exec as parallel PRs, shepherd review/correction waves to merge) and 'when' (Use when the user gives a list of issue numbers ≥ 2 and asks the listed phrases), plus explicit negative triggers.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say — 'spawn codex', 'dispatch codex', 'have codex work on', 'manage the PRs', 'process feedback', 'get them merged' — including synonyms.	5 / 5
Distinctiveness Conflict Risk	Clear niche (multi-issue parallel codex delegation) with a 'Not for...' clause disambiguating sibling skills (codex-task-waves, invoking-codex-exec, /pr), giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ddnetters/homelab-agent-skills
Path: codex-issue-waves/SKILL.md
Commit: 808c382

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.