@steipete: Wrote a skill that runs codex /review in a loop until there's no booboos anymore. Caveat: It won't fix system architect…
Summary
Peter (@steipete) created a skill that runs Codex's /review command in a loop to fix code issues, but notes it doesn't fix system architecture. The associated GitHub repo 'agent-scripts' contains shared agent instructions, skills, and helper scripts for local workspaces.
View Cached Full Text
Cached at: 05/15/26, 03:03 PM
Wrote a skill that runs codex /review in a loop until there’s no booboos anymore.
Caveat: It won’t fix system architecture for ya, so you still need BRAIN as master model. https://t.co/0Z6iJnCqCX
steipete/agent-scripts
Source: https://github.com/steipete/agent-scripts
Agent Scripts
Shared agent instructions, skills, and small portable helpers for Peter’s local workspaces.
This repo is the canonical place for:
AGENTS.MD: shared hard rules for Codex/Claude-style agentsskills/: reusable workflow skills, including repo-owned skills exposed by symlinkscripts/: dependency-light helpers used across projectshooks/: local guardrails such as skill validation
Skills
Skills are the main routing layer. Each skills/<name>/SKILL.md has YAML front matter:
---
name: skill-name
description: "Short generic trigger phrase."
---
Rules:
- Keep descriptions short and generic; optimize for routing, not documentation.
- Keep skill bodies terse and operational.
- Prefer helper scripts under
skills/<name>/scripts/when a workflow has repeatable commands. - Validate after edits:
scripts/validate-skills. - Quote
descriptionin front matter.
Global discovery usually points here:
~/.codex/skills -> ~/Projects/agent-scripts/skills~/.claude/skills -> ~/Projects/agent-scripts/skills
Shared skills live as real folders in skills/. Repo-owned skills stay canonical in their repo and are exposed here with tracked relative symlinks, for example:
skills/discrawl -> ../../discrawl/.agents/skills/discrawl
Current symlinked repo-owned skills include birdclaw, discrawl, gog, imsg, slacrawl, wacli, and wacrawl.
Agent Instructions
Shared hard rules live in AGENTS.MD.
Global setup:
~/.codex/AGENTS.md -> ~/Projects/agent-scripts/AGENTS.MD~/.claude/CLAUDE.md -> ~/Projects/agent-scripts/AGENTS.MD~/.claude/AGENTS.md -> ~/Projects/agent-scripts/AGENTS.MD
Downstream repos should use a pointer-style AGENTS.MD:
READ ~/Projects/agent-scripts/AGENTS.MD BEFORE ANYTHING (skip if missing).
Repo-specific rules go below that pointer. Do not copy the shared blocks into downstream repos.
Helpers
scripts/committer
- Stages exactly the listed files.
- Enforces a non-empty commit message.
- Runs skill validation before committing.
scripts/validate-skills
- Checks every
skills/*/SKILL.md. - Verifies YAML front matter plus required
nameanddescription. - Enable as a local hook with
git config core.hooksPath hooks.
scripts/docs-list.ts
- Walks
docs/. - Enforces
summaryandread_whenfront matter. - Prints onboarding summaries for repos that wire it in.
scripts/browser-tools.ts
- Standalone Chrome DevTools helper.
- Common commands:
start --profile,nav <url>,eval '<js>',screenshot,search --content "<query>",content <url>,inspect,kill --all --force. - Build optional binary with
bun build scripts/browser-tools.ts --compile --target bun --outfile bin/browser-tools.
Syncing
Treat this repo as canonical for shared agent rules and portable helper scripts.
When syncing downstream repos:
- Pull latest here first.
- Ensure each target repo starts with the pointer-style
AGENTS.MD. - Preserve repo-local rules below the pointer.
- Copy helper changes both directions only when the helper is meant to stay byte-identical.
- Keep scripts dependency-free and portable; no repo-specific imports or path aliases.
For submodules, repeat the pointer check inside each subrepo, push those changes, then bump submodule SHAs in the parent repo.
Similar Articles
@mattpocockuk: One thing I've underplayed in my skill set is how customizable it is Specifically the /code-review skill 1. Notice the …
Matt Pocock shares how he customizes the /code-review skill by writing issues into CODING_STANDARDS.md, which the agent then enforces during reviews.
@RayFernando1337: The bugs that cause churn almost never show up in a diff, and you only really catch them when you stop reviewing code a…
A developer shares a workflow using Cursor's Opus 4.8 Max Thinking model with subagent harness, and introduces a GitHub repository with installable skill files for AI coding agents, including a 'running-bug-review-board' skill that performs live QA testing.
@reach_vb: Codex Tip: ask Codex to look through your past sessions and turn repeated prompts into reusable skills + subagents you’…
A tip for using Codex to turn repeated prompts into reusable skills and subagents, improving workflow efficiency for tasks like CI failure checking and PR review.
@steipete: If you run this workflow, ask Fable to make codex the workhorse. https://github.com/steipete/agent-scripts/blob/main/sk…
A GitHub repository by steipete providing shared agent instructions, reusable workflow skills, and helper scripts for configuring Codex and Claude-style AI agents in local development environments.
I replaced a fairly complex Reddit research agent with a Codex skill. I'm starting to think many "agents" should just be skills.
The author argues that many research agent projects can be replaced by 'skills' running inside existing harnesses like Codex, sharing their experience implementing a Reddit customer-research workflow as a Codex skill with only deterministic Python helpers, and questioning when custom agent runtimes are truly needed.