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/release-hygiene.md

View on GitHub
# Release Hygiene Checklist

Run before tagging or releasing, after all review fixes are committed and CI is green. (Moved in v0.2 from the old `build-review-loop.md`, Step 12.)

This is NOT engineering. It is the mechanical release hygiene that recurs every
release. Skipping it produces a tag that points at the wrong commit, version
pins that disagree with the tag, a missing CHANGELOG, and build artifacts
committed to the repo root. The user has corrected this pattern multiple times.

Run these steps after all review fixes are committed and CI is green, BEFORE
creating or moving a tag or publishing a release:

## 1. Bump ALL version pins

Search for the old version string across ALL files, not just the obvious ones:

```bash
grep -rn "0\.4\.0" plugin.yaml pyproject.toml VERSION README.md .claude-plugin/
```

Files that typically carry version pins:
- `plugin.yaml` (version field)
- `pyproject.toml` (version field)
- the entrypoint script (VERSION constant)
- `README.md` (status line)
- `.claude-plugin/plugin.json` (version field)
- `.claude-plugin/marketplace.json` (version field)
- Any `VERSION` file if one exists

Update ALL of them in one commit. The `test_release_versions_agree` test
checks internal consistency (all pins agree with each other) but does NOT
check against the git tag. You must verify manually.

## 2. Add CHANGELOG entry

Add a new `## vX.Y.Z` section at the top of `CHANGELOG.md` (below the
`# Changelog` header). Include:
- One-line summary of the release theme
- Release posture (production-ready, beta, etc.)
- Key changes grouped by feature area
- Review summary (which models reviewed, how many findings, all fixed)

## 3. Remove ALL build artifacts from the repo root

Internal AI workflow files must NEVER be committed to the repo. These include:
- `BRIEF.md`, `BRIEF_*.md`, `FIX_BRIEF_*.md` — spec/brief files for Cursor
- `codex-review.md`, `opus-review.md`, `opus-review-raw.txt` — review outputs
- `review-prompt.md`, `review.diff` — review inputs
- Any `*.diff` files generated for review

```bash
git rm BRIEF*.md FIX_BRIEF*.md *review*.md *review*.txt *review*.diff 2>/dev/null
```

If the repo has pruned these before, it will need to prune them again. The
rule is simple: nothing in the repo root that is not part of the shipped
product. Briefs and reviews go in `/tmp/` or the Hermes workspace, not the repo.

## 4. Move the tag to the final commit

If a tag was created before the hygiene commit, it now points at the wrong
commit. Delete and recreate it:

```bash
git tag -d vX.Y.Z
git tag vX.Y.Z HEAD
git push origin vX.Y.Z --force
```

If a GitHub release exists, delete and recreate it (the API rejects
`gh release edit --target` when the commitish changes):

```bash
gh release delete vX.Y.Z --yes
gh release create vX.Y.Z --prerelease --title "..." --notes "..."
```

## 5. Verify

```bash
# Tag points at the latest commit
git rev-parse vX.Y.Z          # should equal git rev-parse HEAD
# No version drift
grep -rn "0\.4\.0" .          # should return nothing (old version gone)
# No build artifacts in repo root
ls BRIEF*.md *review*.md *review*.diff 2>/dev/null  # should be empty
# CHANGELOG has the new entry
head -3 CHANGELOG.md
# CI green
gh run list --limit 1 --json conclusion -q '.[0].conclusion'
```

## Common failure modes

| Failure | What happens | When it was caught |
|---|---|---|
| Tag points at pre-hygiene commit | Release includes old version pins | An early-beta release |
| Version pins not bumped | Software self-reports 0.4.0 while tag says 0.5.0 | An early-beta release |
| No CHANGELOG entry | Users clone the repo and see no record of what changed | An early-beta release |
| Build artifacts committed | Lead clones repo and finds 530KB diff + AI review transcripts | An early-beta release (pruned twice before) |
| test_release_versions_agree passes | It checks internal consistency, not tag alignment — false confidence | An early-beta release |

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