Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Stages all changes and generates a lean Conventional Commits message via caveman-commit — user reviews and commits manually. Triggers on any commit intent: "commit", "stage my changes", "ready to push", "let's commit", "make a commit", "commit this", "push changes", "squash and commit", or any variation. Use whenever the user signals they're done with changes and ready to commit, even if they don't mention "message" or "caveman". Does NOT run git commit — outputs a ready-to-run command for the user to execute after review.
Autonomous ML research - agent modifies GPT training code, runs 5-min experiments, keeps improvements
Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
AI spend analytics — see where your token budget goes by task, model, tool, and project across 31 AI coding tools including Claude Code. Use when the user asks about AI costs, token usage, spend breakdown, or wants to optimize their AI budget.
A standalone adversarial PLAN-review loop where Claude Code (builder) and OpenAI Codex (read-only critic) tag-team an implementation plan before any code is written. Use this when you ALREADY have a plan or a clear idea and just want the cross-model stress-test — no requirements interview first. Claude drafts/loads the plan into PLAN.md, Codex reviews it in a read-only sandbox and returns VERDICT:APPROVED or VERDICT:REVISE, Claude revises and re-submits to the SAME Codex session (context preserved) until APPROVED or a configurable MAX_ROUNDS cap is hit. Human approves the converged plan before code. Use when the user says "/codex-review", "codex review my plan", "have Codex review my plan", "argue this plan with Codex", "adversarial plan review", "make Claude and Codex argue/fight over the plan", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants a second-model sanity check on the PLAN before implementation. For a guided requirements interview BEFORE the rev
Full memory hygiene cycle — compresses memory-sessions.md, deduplicates memory-decisions.md, and syncs key project facts to the memory MCP graph. Run monthly or when context feels heavy.