Spun up an online entry for your codex-review loop — paste any diff or PR link and your teammates get the review back

[shesl-tinkerland]

@steipete — wired your codex-review skill up as a one-click demo. Upload a diff or paste a PR link, and the review-fix-rerun loop runs in the browser. No Codex CLI install, no API key.

The interesting bit in this SKILL.md isn't the codex review call — it's the stop condition and the rules around which findings to accept, when to refactor vs. patch, and when not to rerun review for cleaner wording. Worth seeing that judgment exercised against inputs you didn't write yourself.

The demo is pinned to the codex-review contract as it stood before the upstream rename to skills/autoreview, so the tweet's link still leads somewhere usable.

Feel free to close if this isn't relevant. — Songlin, building Socialistic so skill authors can see how their SKILL.md actually gets used.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Latest ClawSweeper review: 2026-05-24 03:43 UTC / May 23, 2026, 11:43 PM ET.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Summary
Keep open under the conservative personal-repository policy: this is an external hosted demo/support announcement, not an in-repo defect, and the provided policy does not enable automated cleanup closure for this repository.

Reproducibility: not applicable. This issue announces an external demo rather than reporting a reproducible bug. Source inspection found the relevant repo surface is now autoreview, but no failing in-repo behavior is described.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Share version, platform, channel/provider, and relevant config details.

Next step
No autonomous source repair is appropriate; the remaining action is maintainer policy triage for an external service announcement.

Review details

Best possible solution:

Have a maintainer decide whether to acknowledge the external demo or close it as outside the tracker; only document or link it if the maintainer wants to support that hosted path.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this issue announces an external demo rather than reporting a reproducible bug. Source inspection found the relevant repo surface is now autoreview, but no failing in-repo behavior is described.

Is this the best way to solve the issue?

Not applicable as a code fix; there is no proposed patch or requested source change. The narrow maintainable path is maintainer triage of whether the external demo should be acknowledged, documented, or closed as out-of-tracker.

Label changes:

• add P3: This is a low-risk support/demo announcement with no reported runtime defect or urgent user impact.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P3: This is a low-risk support/demo announcement with no reported runtime defect or urgent user impact.

What I checked:

• Issue context: The provided issue body announces an external Socialistic demo, says it is pinned to the old codex-review contract before the upstream rename, and explicitly leaves relevance/closure to the maintainer.
• Current repository scope: README.md scopes the repo to shared agent instructions, reusable skills, and portable helper scripts. (README.md:5, f0d35d0ac44d)
• Autoreview is the current skill surface: README.md documents public shared skills as symlinks and shows skills/autoreview -> ../../agent-skills/skills/autoreview. (README.md:33, f0d35d0ac44d)
• Rename documented on current main: CHANGELOG.md says the old codex-review skill was replaced with autoreview while keeping Codex as the default/recommended review engine. (CHANGELOG.md:20, f0d35d0ac44d)
• Skill history provenance: Commit e6d810d added skills/autoreview and deleted skills/codex-review; commit d802d16 later made skills/autoreview a tracked symlink. (skills/autoreview, e6d810d5fe11)
• Repository cleanup policy: The provided repository state says this repo uses the generic personal-repository onboarding profile and should not auto-close issues or pull requests unless a repository-specific profile later enables that policy.

Likely related people:

• steipete: Peter Steinberger authored the original codex-review skill, the autoreview replacement, the current autoreview symlink, and the README/changelog docs around this skill surface. (role: feature owner and recent area contributor; confidence: high; commits: f9678c9245ea, e6d810d5fe11, d802d16f62d2; files: skills/codex-review, skills/autoreview, README.md)

Remaining risk / open question:

• No repository-specific cleanup profile authorizes automated closure for this personal repository.
• The item concerns an external hosted service rather than a concrete in-repo source change, so maintainer preference determines whether it belongs in the tracker.

Codex review notes: model gpt-5.5, reasoning high; reviewed against f0d35d0ac44d.