request-re-review

Stars8

Forks0

UpdatedMay 18, 2026 at 04:55

Push changes on the current PR branch and request a fleet re-review. Use when the user says "request re-review", "push and re-review", "push for re-review", "I'm done with this PR have the fleet re-review", or "update PR and get it reviewed again". Also useful when the user has manually edited a PR branch in any pane and wants the fleet review pipeline to pick it back up.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

jakildev

jakildev/IrredenEngine

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	request-re-review
description	Push changes on the current PR branch and request a fleet re-review. Use when the user says "request re-review", "push and re-review", "push for re-review", "I'm done with this PR have the fleet re-review", or "update PR and get it reviewed again". Also useful when the user has manually edited a PR branch in any pane and wants the fleet review pipeline to pick it back up.

request-re-review

Preconditions

You are on a PR branch (not a scratch branch, not master).
There is an open PR for this branch.
gh is authenticated.

Flow

1. Identify the current PR

git branch --show-current

Find the open PR for this branch:

gh pr list --state open --head <branch-name> --json number,title,labels

If no PR is found, tell the user and stop.

2. Commit and push any pending changes

Invoke the commit-and-push skill to stage, commit, and push any uncommitted changes on this branch. If the working tree is already clean and all commits are pushed, skip to step 3.

3. Swap labels to request re-review

Remove stale fleet verdict labels and add the re-review request:

gh pr edit <N> --remove-label "fleet:approved" --remove-label "fleet:needs-fix" --remove-label "fleet:blocker" --add-label "human:re-review"

4. Post a comment

gh pr comment <N> --body "Human made changes — re-review requested."

5. Release the branch

Invoke the start-next-task skill to reset to a scratch branch off origin/master. This frees the PR branch so reviewers (or other agents) can check it out.

6. Report back

Print:

Re-review requested for PR #<N> (<title>).
- Label: human:re-review added, fleet:approved removed
- Branch released — reviewers can check it out
- Next reviewer pass will pick it up

Anti-patterns

Leaving the PR branch checked out after requesting re-review. The whole point is to release it for reviewers.
Using this on a PR that's still fleet:wip — that PR isn't ready for review at all. Tell the user to finalize first.
Force-pushing. Never --force.

More from this repository

same repository

review-pr

jakildev/IrredenEngine

Review an open GitHub PR on the Irreden Engine repo and post a structured review. Use when the user says "review PR <N>", "review #<N>", "review the last PR", "check my PR", "review any new PRs", "review the PR queue", "check for new PRs to review", "review the open PRs", or otherwise asks for a code review — and also invoke automatically from a persistent reviewer-loop session when `gh pr list` surfaces a PR that has not yet been reviewed by this fleet. Designed to be invoked by a dedicated reviewer agent (dispatched into a pool worktree) whose job is to look at another agent's work with a fresh context. Writes a structured review covering ownership, ECS invariants, allocation hot paths, naming, tests, and project-specific smells, then posts it as a PR comment.

2026-07-268

simplify

jakildev/IrredenEngine

Polish the dirty working tree before committing — catch Irreden-Engine smells that a reviewer would otherwise flag. Use whenever you're about to commit, after addressing review feedback, after amending a commit, or whenever the user says "simplify", "clean up", "polish", "self-review", or "review my changes". Also auto-invoked by commit-and-push before the commit message is drafted. The skill finds per-entity getComponent in tick functions, allocation in hot loops, ECS naming convention slips, opportunities to reuse existing helpers, dead code, debug logs left behind, tautological comments, triple-nested loops over voxel volumes, renderer leaks from creation code, CPU-side SDF grid evaluation, linear-search in save/load hot paths, and stale or drifting CLAUDE.md / role / skill docs. Dispatches a parallel reuse-detection subagent fan-out so the reuse pass runs concurrently with the main checks. Applies safe fixes inline and reports anything that needs human judgment. Saves a review-fix-rereview round-trip.

2026-07-268

commit-and-push

jakildev/IrredenEngine

Stage, commit, push a feature branch, and open a GitHub PR against master for the Irreden Engine repo. Use whenever the user says "commit", "commit my changes", "commit and push", "open a PR", "make a PR", "wrap up this chunk", or otherwise indicates the current slice of work is ready for review. The skill assumes the parallel-agent workflow where work happens on short-lived feature branches, another agent reviews the PR, and the user merges via the GitHub UI. NEVER commit directly to master.

2026-07-218

platform-catchup

jakildev/IrredenEngine

Process the backlog of `fleet:needs-<host>-smoke` PRs on the current host. Builds a representative demo cohort against current `origin/master`, runs each with `--auto-screenshot`, and on green batch-swaps `fleet:needs-<host>-smoke` → `fleet:verified-<host>` on every eligible merged PR. On red (build break), files / opens a fix PR for the offender and holds labels on PRs that touch the implicated source paths until the fix lands. On partial (per-demo runtime hang or crash but build green), sweeps the rest, then fix-forwards the offending demo this session (issue only as the documented fallback). Runs on Linux, macOS, AND native Windows (MSYS2 mingw64) — Windows is now the primary validation host. Use when the human cues "platform-catchup", "catch up smoke tests", or "catch up Windows builds". Skill is **cue-only**, never auto-run — multi-target builds and ~40-demo runs are expensive, the human chooses when to spend them.

2026-07-158

render-debug-loop

jakildev/IrredenEngine

Build, run, and visually evaluate a rendering demo in an automated loop. Captures screenshots across a demo's configured shot list (zoom, camera offset, render-mode combinations), reads each image, diagnoses rendering issues against a topic-indexed reference (trixel / SDF shapes, lighting, backend parity), applies fixes, and repeats. Use whenever iterating on render pipeline bugs, shape alignment, lighting, parity drift, or any visual regression in the engine.

2026-07-158

render-verify

jakildev/IrredenEngine

Automated pass/fail render-regression harness for Irreden Engine demos. Wraps build → run → capture → compare → report: builds a demo, runs it with `--auto-screenshot`, then compares each shot against a committed reference image using a stdlib-only Python comparator. Reports per-shot pass/fail with diff images written for mismatches. Use after any render pipeline change to catch visual regressions automatically, or as a sanity pass on `master` before cutting releases.

2026-07-158

name	request-re-review
description	Push changes on the current PR branch and request a fleet re-review. Use when the user says "request re-review", "push and re-review", "push for re-review", "I'm done with this PR have the fleet re-review", or "update PR and get it reviewed again". Also useful when the user has manually edited a PR branch in any pane and wants the fleet review pipeline to pick it back up.

request-re-review

Preconditions

You are on a PR branch (not a scratch branch, not master).
There is an open PR for this branch.
gh is authenticated.

Flow

1. Identify the current PR

git branch --show-current

Find the open PR for this branch:

gh pr list --state open --head <branch-name> --json number,title,labels

If no PR is found, tell the user and stop.

2. Commit and push any pending changes

Invoke the commit-and-push skill to stage, commit, and push any uncommitted changes on this branch. If the working tree is already clean and all commits are pushed, skip to step 3.

3. Swap labels to request re-review

Remove stale fleet verdict labels and add the re-review request:

gh pr edit <N> --remove-label "fleet:approved" --remove-label "fleet:needs-fix" --remove-label "fleet:blocker" --add-label "human:re-review"

4. Post a comment

gh pr comment <N> --body "Human made changes — re-review requested."

5. Release the branch

Invoke the start-next-task skill to reset to a scratch branch off origin/master. This frees the PR branch so reviewers (or other agents) can check it out.

6. Report back

Print:

Re-review requested for PR #<N> (<title>).
- Label: human:re-review added, fleet:approved removed
- Branch released — reviewers can check it out
- Next reviewer pass will pick it up

Anti-patterns

Leaving the PR branch checked out after requesting re-review. The whole point is to release it for reviewers.
Using this on a PR that's still fleet:wip — that PR isn't ready for review at all. Tell the user to finalize first.
Force-pushing. Never --force.