Skip to content

moonlight-lupin/agent-skills / plugins/dev-pipeline/skills/review-commit

review-commit

Verified

Use when the user says 'review loop N times', 'build then review', 'fix and re-review', 'review loop until clean', 'have cursor build, codex review', or wants the dev-pipeline review stage: a two-axis single pass (Standards + Spec, parallel, never merged) FIRST, then a budgeted confirm-round loop on the fix diffs until no BLOCKING/MAJOR is open, then the commit/deploy gate — three-reviewer gate before live deploy, release hygiene before tagging. Also triggers: 'two-axis review', 'confirm rounds', 'review diff until SHIP', 'N confirm rounds', ship gate.

FileKindSize
SKILL.mdexecutableskill md6.8 KB
references/background-build-polling.mdexecutablescript3.9 KB
references/confirm-round-protocol.mdexecutablescript12.3 KB
references/dispatch-result-contract.mdexecutablescript3.5 KB
references/feature-build-brief.mdexecutablescript2.9 KB
references/fix-brief-template.mdexecutablescript10.5 KB
references/persistent-loop-plan.mdexecutablescript6.9 KB
references/release-hygiene.mdexecutablescript3.9 KB
references/reviewer-dispatch.mdexecutablescript6.0 KB
references/spec-convergence.mdexecutablescript5.2 KB
references/two-axis-single-pass.mdexecutablescript9.9 KB
references/workflow-steps.mdexecutablescript18.9 KB
scripts/attest_file.pyexecutablescript2.7 KB
scripts/capture_dispatch_result.pyexecutablescript3.6 KB
scripts/loop_plan_check.pyexecutablescript3.8 KB

references/feature-build-brief.md

View on GitHub
# Feature Build Brief (new capability, not a fix)

Companion to fix-brief-template.md. Use when dispatching the builder to ADD a
capability against contract tests the orchestrator already wrote and committed
(SKILL.md Step 2b pattern). Field-validated shape for two-builder parallel
dispatch on one repo.

## Structure

```markdown
# BRIEF-N: <capability title>

## Repo / working rules

<BUILDER BLOCK — paste verbatim from orchestrator/references/coding-principles.md § Builder block>

- Repo path, branch (already checked out).
- Do NOT `git commit` — the orchestrator commits after verification.
- Do NOT modify (exact file list): the orchestrator-written contract test files,
  fixtures, cached schemas. "If the tests contradict this brief, STOP and report
  the contradiction — do not warp production code or weaken tests."
- For parallel dispatch: name the OTHER builder's tree and forbid touching it.

## Task (what to build)
<The target artifact layout, exact CLI surface, field-by-field mapping rules,
validation requirements. Quote the governing spec's section numbers where they
bite. Specify fallback behavior for missing dependencies.>

### Acceptance criteria (numbered, each runnable)
1. `python -m pytest <contract-test-file> -q` — ALL N tests pass.
2. `python -m pytest <existing-suite> -q` — existing tests still pass.
3. (combined run command)
4. `--help` shows the new flag/surface.
5. No-regression check spelled out concretely (what must be byte-equivalent).
6. Dependency policy ("no new pip dependencies" unless approved).

### Verification you must run and report
- The pytest commands with output.
- A manual end-to-end run: exact commands, then show the artifacts
  (`find <out> -type f | sort`, `cat` the key files).

## Integration boundaries changed
| Boundary | Old shape | New shape | Test |
```

## What makes it work
- **Contract tests committed BEFORE the brief is sent** — the brief names the
  test file that encodes the expected behavior and repeats the do-not-modify rule.
- **Acceptance criteria are exact commands, not descriptions** — the builder
  runs them and pastes output; the orchestrator re-runs them independently.
- **Forbidden files are listed by path**, not by description.
- **Parallel dispatch needs three things per brief:** its own directory scope,
  the sibling scope forbidden, and its own log file + terminal session
  (pitfall (parallel dispatches)). Commit in completion order after verifying each independently.
- **A builder that stops to report a contradiction is a success signal**
  (see `review-lessons/references/review-findings-adjudication.md` — own the fixture fix) — the brief must license that stop explicitly.
- **Map rules field-by-field when the contract is a spec** — name every
  permitted field, its source in the input format, and its transformation
  (string → object, placeholder rewrites, slug constraints). A builder given
  "convert the manifest" guesses; one given the table converts correctly.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall