Skill Claude CodeCodex
Analyze open GitHub issues, group them into thematic arcs, and write a sprint file for orchestrator context. Use when deciding what to work on next, assessing board health, or updating strategic context.
Skill Claude CodeCodex
Build an autonomous sprint skill for a target project. Explores the project's workflows, constraints, and tooling, then produces a tailored sprint skill that lets Claude orchestrate parallel implementation sessions end-to-end. Use when setting up auto-sprint in a new repo, or when adapting sprint orchestration to a…
Skill Claude CodeCodex
Review recent PRs in a feature area for architectural consistency, missed integration points, duplicated patterns, and wrong directions. File issues for problems found. Use after 3-4 related issues merge or when a session's cost exceeds $15.
Skill Claude CodeCodex
Backfill diary entries from Claude Code session transcripts. Extracts insights, learnings, and patterns from past sessions and writes structured diary entries to .claude/diary/. Use when the user says "write diary", "backfill diary", "/diary", "what did we do today", or wants to capture session learnings. Also use…
Skill Claude CodeCodex
Post-implementation triage: measure actual diff metrics to determine review depth. Run after implement, before review. Usage: /estimate (in a worktree with changes).
Skill Claude CodeCodex
Full-text search of Claude Code session histories to find and resume past conversations. Use when user says "find session", "search sessions", "find that conversation where", "what were my last sessions", or wants to locate a previous Claude session.
Skill Claude CodeCodex
Mine flaky test failures from Claude Code session transcripts. Scans JSONL session files for test failure patterns in tool results, aggregates by test file and name, and reports which tests fail across multiple sessions. Use when investigating test reliability, after a sprint to check for new flaky tests, or when the…
Skill Claude CodeCodex
Audit and garbage-collect a committed Claude-memory store (MEMORY.md + per-fact files). Evidence-based, parallel, then a gated apply. Use when MEMORY.md has grown large, after several sprints, when memory has drifted from CLAUDE.md, or when the user says "/memory-gc", "clean up memory", "audit memory", "the memory is…
Skill Claude CodeCodex
Author, refine, or migrate a doing-it-wrong architectural rule, and harvest recurring mistakes from merged PRs. Routes on its argument — harvest (mine PR review comments for recurring author mistakes), init (bootstrap the rule engine into a repo), add (author a rule), or no arg (overview + "is this a good rule?"…
Skill Claude CodeCodex
Extract actionable lessons from sprint history. Buckets every Claude Code session into the sprint it ran in, builds a deterministic per-session digest (tokens, duration, errors, orchestration signals, evidence), then runs a multi-agent Workflow that classifies each session (orchestrator vs worker), scans for tool…
Skill Claude CodeCodex
Sprint lifecycle: plan, run, review, retro. The top-level orchestrator for autonomous issue resolution. Use for "run a sprint", "plan the sprint", "sprint review", "sprint retro", "/sprint", "/sprint plan", "/sprint review", "/sprint retro", or any variant.
Skill Claude CodeCodex
Step back and interrogate the frame instead of executing it. /why GENERATES the sharp questions that should have been asked about a request, plan, artifact, or your own intended action — it does NOT answer them. Use when handed an assignment that smells mis-scoped, when about to loosen a constraint to silence a signal…
Skill Claude CodeCodex
Use the mcx CLI via Bash instead of native MCP tools. This eliminates 15,000+ tokens of tool definitions per server from every conversation context.