start-next-task

Estrellas8

Forks0

Actualizado2 de junio de 2026 a las 21:13

Reset the current worktree to a fresh feature branch for the next chunk of work. In the standard case that means branching off the latest origin/master; if the worker has an active fleet-claim molecule (fleet stack mode) or the human cued cursor-flow stacking, the new branch instead bases on the just-opened PR's head ref so the downstream task's diff stays isolated. Use after commit-and-push has opened a PR and the user (or you) wants to move on to the next task, OR whenever the user says "next task", "start next", "move on", "pull master and start fresh", "I merged it", "back to master", "fresh start", "new task", or cues stacking with "stack this", "next slice stacked", "keep stacking", "stack the next on this PR".

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

jakildev

jakildev/IrredenEngine

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name

start-next-task

description

start-next-task (Irreden Engine)

The flow lives in docs/agents/skills/start-next-task.md. Read it first, then apply the engine deltas below. This wrapper carries deltas only — see docs/design/skill-sharing.md for why.

Deltas (Irreden Engine)

Delta key	Engine value
default branch	`master`
remote	`origin`
branch prefix	`claude/`
worktree-assert command	`fleet-assert-worktree` (optionally `fleet-assert-worktree <worktree-basename>`)
fleet doc	`docs/agents/FLEET.md` — see "Stacking in cursor flow"
area examples	`engine`, `render`, `game`, plus module names (`engine/voxel`, etc.)

Concrete branch-name examples for the engine:

Standard: claude/engine-velocity-drag-refactor, claude/render-lod-threshold-tuning, claude/game-save-format.
Cursor stack: claude/render-glow-pulse-tuning (stacked on claude/render-glow-pulse).
Fleet stack: claude/1234-occupancy-grid (issue-number prefix).

Engine notes

fleet-issue view <issue#> is the cache-aware title lookup used in step 5's fleet-stack branch-name derivation; it falls back to gh issue view.
The macOS Cursor sandbox is the concrete case of the shared flow's "sandbox note" — run the git checkout -B and the git config branch.<new>.cursor-stack-base writes with the all permission so .git/config is actually written.

Más de este repositorio

mismo repositorio

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

start-next-task

description

start-next-task (Irreden Engine)

The flow lives in docs/agents/skills/start-next-task.md. Read it first, then apply the engine deltas below. This wrapper carries deltas only — see docs/design/skill-sharing.md for why.

Deltas (Irreden Engine)

Delta key	Engine value
default branch	`master`
remote	`origin`
branch prefix	`claude/`
worktree-assert command	`fleet-assert-worktree` (optionally `fleet-assert-worktree <worktree-basename>`)
fleet doc	`docs/agents/FLEET.md` — see "Stacking in cursor flow"
area examples	`engine`, `render`, `game`, plus module names (`engine/voxel`, etc.)

Concrete branch-name examples for the engine:

Standard: claude/engine-velocity-drag-refactor, claude/render-lod-threshold-tuning, claude/game-save-format.
Cursor stack: claude/render-glow-pulse-tuning (stacked on claude/render-glow-pulse).
Fleet stack: claude/1234-occupancy-grid (issue-number prefix).

Engine notes

fleet-issue view <issue#> is the cache-aware title lookup used in step 5's fleet-stack branch-name derivation; it falls back to gh issue view.
The macOS Cursor sandbox is the concrete case of the shared flow's "sandbox note" — run the git checkout -B and the git config branch.<new>.cursor-stack-base writes with the all permission so .git/config is actually written.