review-fix-signoff-loop

Name: review-fix-signoff-loop
Author: AgentWorkforce

769stars58forks

How to install review-fix-signoff-loop?

agentworkforce/relay/review-fix-signoff-loop

$npx -y skills add AgentWorkforce/relay --skill review-fix-signoff-loop

Installs into the current project.

Summary

Use when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents, typically Claude and Codex, both agree the work is comprehensively complete. Covers fresh-context iterations, repairable gates, du

Files · 1

View on GitHub

SKILL.md

1	### Purpose
2
3	Use this pattern for high-stakes implementation workflows where a normal "implement, test, review once" flow is not enough. The workflow must keep repairing and re-reviewing until independent signoff agents agree the spec is fully wired end to end.
4
5	Pair this with `writing-agent-relay-workflows` for SDK syntax and `relay-80-100-workflow` for deterministic validation gates.
6
7	### Required Shape
8
9	- Run deterministic preflight before agents start.
10	- Confirm repository root, required specs, declared write scope, credentials needed for PR comments, and whether commit/push/PR creation is in scope.
11	- For cross-repo or package-release work, write a scope matrix before implementation: repositories, branches, PRs, packages, providers/features touched, published versions, consuming package manifests, lockfiles, and expected downstream bumps.
12	- Probe the CLIs used by later agent steps. For Codex, `codex login status` is not enough; run a tiny `codex exec --ephemeral --json --sandbox read-only -m <supported-model>` prompt and fail early with a clear re-login instruction if it cannot return the expected token.
13	- Write preflight evidence to `.workflow-artifacts/<workflow>/iteration-N/preflight.md`.
14	- Implement with scoped owners.
15	- Use Codex workers for code changes unless the codebase has a reason to prefer another CLI.
16	- Split backend, frontend, desktop, tests, docs, or infrastructure into explicit non-overlapping ownership areas.
17	- Each worker writes a durable summary artifact with changed files and commands run.
18	- Reconcile before validation.
19	- Add a deterministic `implementation-reconcile` gate that checks required files, expected API/UI/runtime surfaces, migrations, generated artifacts, and untracked files with `git status --short -- <paths>`.
20	- For multi-provider changes, reconcile against the scope matrix: every touched provider/package must be classified as `implemented`, `dependency-only`, `intentionally-deferred`, or `not-applicable`, with proof. Do not let "we only bumped the package I remembered" pass this gate.
21	- For package-release flows, reconcile producer and consumer state: `npm view <pkg> version`, package manifests, lockfile resolved tarballs/integrities, and `npm ls <pkg>` from every consuming workspace.
22	- For CI failures, map each failing job to its exact local command or documented non-local equivalent. Distinguish similarly named gates (for example handler coverage vs acceptance route coverage) and replay the one that actually failed.
23	- Use `failOnError: false`, then route the captured output to a repair owner.
24	- Run repairable validation.
25	- Use capture -> fix -> rerun for typecheck, targeted tests, integration or E2E tests, and regression checks.
26	- Include exact failing CI commands when available before broader "nearby" checks. A nearby green gate is supporting evidence, not proof that the reported CI failure is fixed.
27	- Red validation output is input for a repair agent, not an immediate workflow failure.
28	- Write `BLOCKED_NO_COMMIT.md` only for true external blockers.
29	- Run fresh-context signoff reviews.
30	- Start a new workflow run, new agent names, or otherwise new agent contexts for each loop iteration.
31	- Run Claude and Codex signoff reviews independently over the same post-validation repo state.
32	- Reviewers must read specs, diff, validation logs, artifacts, and actual files.
33	- Break only on dual signoff.
34	- The loop may exit only when both reviewers write the exact satisfied verdict and final deterministic acceptance is green.
35	- If either reviewer finds issues or is blocked, run a Codex fix pass and start a new fresh-context review iteration.
36	- Make the Codex fix pass a non-interactive one-shot worker (`preset: 'worker'`) with a `file_exists` verification for its durable report. Do not rely on interactive PTY idle detection or `/exit` for loop progress.
37	- Report final signoff.
38	- Write a final `SIGNOFF.md` that includes iteration count, validation evidence, Claude rationale, Codex rationale, remaining risks, and artifact paths.
39	- Include the final scope matrix with every repository/package/provider row signed off, deferred with owner/date, or marked not applicable. For release flows, include published and consumed versions.
40	- Post the same report to the PR. Resolve the PR from an explicit env var first, then from `gh pr view`.
41
42	### Verdict Contract
43
44	#### Use a strict text contract so deterministic gates can parse the result:
45
46	```text
47	VERDICT: COMPREHENSIVELY_SATISFIED \| FINDINGS \| BLOCKED
48	why_passed: required when VERDICT is COMPREHENSIVELY_SATISFIED
49	end_

People who liked this also viewed

6 picks

Type

review-fix-signoff-loop

769stars58forks

View on GitHub

How to install review-fix-signoff-loop?

agentworkforce/relay/review-fix-signoff-loop

$npx -y skills add AgentWorkforce/relay --skill review-fix-signoff-loop

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	### Purpose
2
3	Use this pattern for high-stakes implementation workflows where a normal "implement, test, review once" flow is not enough. The workflow must keep repairing and re-reviewing until independent signoff agents agree the spec is fully wired end to end.
4
5	Pair this with `writing-agent-relay-workflows` for SDK syntax and `relay-80-100-workflow` for deterministic validation gates.
6
7	### Required Shape
8
9	- Run deterministic preflight before agents start.
10	- Confirm repository root, required specs, declared write scope, credentials needed for PR comments, and whether commit/push/PR creation is in scope.
11	- For cross-repo or package-release work, write a scope matrix before implementation: repositories, branches, PRs, packages, providers/features touched, published versions, consuming package manifests, lockfiles, and expected downstream bumps.
12	- Probe the CLIs used by later agent steps. For Codex, `codex login status` is not enough; run a tiny `codex exec --ephemeral --json --sandbox read-only -m <supported-model>` prompt and fail early with a clear re-login instruction if it cannot return the expected token.
13	- Write preflight evidence to `.workflow-artifacts/<workflow>/iteration-N/preflight.md`.
14	- Implement with scoped owners.
15	- Use Codex workers for code changes unless the codebase has a reason to prefer another CLI.
16	- Split backend, frontend, desktop, tests, docs, or infrastructure into explicit non-overlapping ownership areas.
17	- Each worker writes a durable summary artifact with changed files and commands run.
18	- Reconcile before validation.
19	- Add a deterministic `implementation-reconcile` gate that checks required files, expected API/UI/runtime surfaces, migrations, generated artifacts, and untracked files with `git status --short -- <paths>`.
20	- For multi-provider changes, reconcile against the scope matrix: every touched provider/package must be classified as `implemented`, `dependency-only`, `intentionally-deferred`, or `not-applicable`, with proof. Do not let "we only bumped the package I remembered" pass this gate.
21	- For package-release flows, reconcile producer and consumer state: `npm view <pkg> version`, package manifests, lockfile resolved tarballs/integrities, and `npm ls <pkg>` from every consuming workspace.
22	- For CI failures, map each failing job to its exact local command or documented non-local equivalent. Distinguish similarly named gates (for example handler coverage vs acceptance route coverage) and replay the one that actually failed.
23	- Use `failOnError: false`, then route the captured output to a repair owner.
24	- Run repairable validation.
25	- Use capture -> fix -> rerun for typecheck, targeted tests, integration or E2E tests, and regression checks.
26	- Include exact failing CI commands when available before broader "nearby" checks. A nearby green gate is supporting evidence, not proof that the reported CI failure is fixed.
27	- Red validation output is input for a repair agent, not an immediate workflow failure.
28	- Write `BLOCKED_NO_COMMIT.md` only for true external blockers.
29	- Run fresh-context signoff reviews.
30	- Start a new workflow run, new agent names, or otherwise new agent contexts for each loop iteration.
31	- Run Claude and Codex signoff reviews independently over the same post-validation repo state.
32	- Reviewers must read specs, diff, validation logs, artifacts, and actual files.
33	- Break only on dual signoff.
34	- The loop may exit only when both reviewers write the exact satisfied verdict and final deterministic acceptance is green.
35	- If either reviewer finds issues or is blocked, run a Codex fix pass and start a new fresh-context review iteration.
36	- Make the Codex fix pass a non-interactive one-shot worker (`preset: 'worker'`) with a `file_exists` verification for its durable report. Do not rely on interactive PTY idle detection or `/exit` for loop progress.
37	- Report final signoff.
38	- Write a final `SIGNOFF.md` that includes iteration count, validation evidence, Claude rationale, Codex rationale, remaining risks, and artifact paths.
39	- Include the final scope matrix with every repository/package/provider row signed off, deferred with owner/date, or marked not applicable. For release flows, include published and consumed versions.
40	- Post the same report to the PR. Resolve the PR from an explicit env var first, then from `gh pr view`.
41
42	### Verdict Contract
43
44	#### Use a strict text contract so deterministic gates can parse the result:
45
46	```text
47	VERDICT: COMPREHENSIVELY_SATISFIED \| FINDINGS \| BLOCKED
48	why_passed: required when VERDICT is COMPREHENSIVELY_SATISFIED
49	end_

People who liked this also viewed

6 picks

Type