spec-dev-review

Estrelas12

Forks3

Atualizado20 de julho de 2026 às 17:03

Writes a scoped spec packet for one ticket, reviewed by a genuinely independent adversarial pass that also regression-checks prior findings. Read-only outside the draft — never writes the canonical spec.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

ayeshakhalid192007-dev

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	spec-dev-review
description	Writes a scoped spec packet for one ticket, reviewed by a genuinely independent adversarial pass that also regression-checks prior findings. Read-only outside the draft — never writes the canonical spec.

spec-dev-review procedure

The prompt carries intent; this skill carries the procedure — keep it a checklist, not an essay. Adapted from Forward Future Loop Library #21 (Ximanta) to this library's L1-first, report-only shape.

Write the packet — for the ticket or story: findings, progress, task plan, and a rubric with critical gates and edge cases derived from that ticket.
Verify claims — every factual claim about the code must be checked against the actual repo before it goes in the packet. Never assert something you haven't read.
Review, genuinely independently — a distinct pass (the loop-verifier agent, or a second claude -p / opencode run call — never the drafting pass grading itself) checks the packet against the rubric and confirms every prior finding is still resolved, not just that new issues are caught.
Fix consistently — if the review finds material issues, fix every affected section of the packet (not just the one the reviewer pointed at), append the finding and fix to the review log, and review again.
Write spec-packet-draft.md: the current packet.
Record — update spec-dev-review-state.md's round count and review log, append one line to loop-run-log.md, commit both.
Take NO other action — this is a draft, never the project's canonical spec. Stop when the reviewer returns ready with no material findings, or when the round cap (5) is reached — log the remaining blocker for human decision.

Mais deste repositório

mesmo repositório

stale-safe-batch-release

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Reviews pending PRs, excludes stale/unfinished work, combines the rest into a release batch built from main. Read-only — reports the batch, never actually releases.

2026-07-2012

codex-completion-contract

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Defines every required outcome and its evidence before acting on long-running work, then audits each requirement as proved/weak/missing/ contradicted. Only run when explicitly asked for a completion audit.

2026-07-2012

loop-harness-verification

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

General-purpose harness for scheduled repo work — stage in an isolated worktree, verify with a genuinely separate second session, ship only after a pass. Read-only — reports, never delivers.

2026-07-2012

clodex-adversarial-review

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Runs an adversarial review cycle against a PR (Claude implements/fixes, Codex or a subagent stand-in reviews), up to 5 iterations. Read-only on the real PR — drafts fixes, never pushes them.

2026-07-2012

ticket-to-pr-ready

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Turns a ticket or bug report into a review-ready patch. Read-only — reproduces, roots out the cause, drafts a fix, reports it. Never opens a PR, never folds in unrelated refactors.

2026-07-2012

repo-cleanup-loop

ayeshakhalid192007-dev/LoopEngineering-CrashCourse

Inspects branches, PRs, commits, and worktrees for what's stale vs. valuable. Read-only. Never deletes uncertain work or someone else's PR without confirmation.

2026-07-2012

name	spec-dev-review
description	Writes a scoped spec packet for one ticket, reviewed by a genuinely independent adversarial pass that also regression-checks prior findings. Read-only outside the draft — never writes the canonical spec.

spec-dev-review procedure

Write the packet — for the ticket or story: findings, progress, task plan, and a rubric with critical gates and edge cases derived from that ticket.
Verify claims — every factual claim about the code must be checked against the actual repo before it goes in the packet. Never assert something you haven't read.
Review, genuinely independently — a distinct pass (the loop-verifier agent, or a second claude -p / opencode run call — never the drafting pass grading itself) checks the packet against the rubric and confirms every prior finding is still resolved, not just that new issues are caught.
Fix consistently — if the review finds material issues, fix every affected section of the packet (not just the one the reviewer pointed at), append the finding and fix to the review log, and review again.
Write spec-packet-draft.md: the current packet.
Record — update spec-dev-review-state.md's round count and review log, append one line to loop-run-log.md, commit both.
Take NO other action — this is a draft, never the project's canonical spec. Stop when the reviewer returns ready with no material findings, or when the round cap (5) is reached — log the remaining blocker for human decision.