alpha-skills

Use when the user asks to run owner-clean on your work, commit the bounded work, merge develop or the current branch into main/master, run pnpm verify or the repository's release gate, push main/master plus develop/current branch to remote, and end back on develop when available. Applies across software repositories. Requires a clean worktree after the owned commit before branch switching, merging, verifying release, or pushing. Keeps unrelated work out of the commit, prefers fast-forward merges, allows normal merge commits when the repo's branch history requires them, verifies before/after commit, and reports exact branch/push state.

Use for one bounded Dalio-style improvement pass on non-trivial work: define a clear goal, identify specific problems, diagnose root causes, design the smallest entropy-reducing plan, do the work, verify it, and name the next target.

Investigate a concrete bug report, isolate the failing seam, carry the work through the smallest defensible fix, add focused regression coverage, and verify the affected path before broadening validation. Use when a user reports a bug, regression, flaky behavior, broken interaction, or "this stopped working" symptom and wants diagnosis plus an actual landed fix, not just speculation or a likely cause.

Post-change ownership and cleanup pass for Codex's own work. Use when the user asks to run owner-check and clean on your work, audit recent edits before finishing, patch bugs found during verification, make a completed change leaner without product drift, or ensure an implementation is owned at the right seam before reporting done.

Use when the user asks for a technical plan, PR breakdown, rollout plan, or refactor plan for stateful systems, especially ones involving authoritative ownership, mirrored state, reconnect behavior, transport protocols, React effects, cached bootstrap payloads, or cross-process/window sync. This skill hardens plans by forcing explicit ownership boundaries, allowed and forbidden triggers, reconnect/cache rules, negative invariants, and loop-prevention regressions.

Design and refine terminal TTY/TUI command flows for CLIs, especially pickers, menus, status screens, and interactive prompts. Use when work involves raw terminal mode, ANSI styling, session or symbol selectors, keyboard-driven CLI menus, or making terminal UX more scannable and reliable across terminal emulators.

Audit writing for signs commonly associated with AI-generated or machine-edited prose. Use when reviewing drafts, articles, docs, comments, PR text, marketing copy, or pasted writing to identify AI-writing tells, separate observations from inferences, and revise toward natural, specific prose without making unsupported authorship claims.

Project-agnostic, behavior-preserving cleanup, semantic clarity refactor, codebase slimming, test audit, and intentional git commit workflow for existing codebases. Use when Codex needs to clean up a changed area, make code leaner without product changes, reduce ambiguity in names, types, fields, status objects, or string unions, remove dead or misleading code, cut bloat and excess indirection, collapse duplicate branches, align nearby tests with the real contract, trim brittle or duplicate tests, add focused regression coverage, or commit the resulting unstaged work with a well-scoped commit message. Trigger on requests like 'clean this up and commit it', 'make this leaner then commit', 'remove dead code and commit', 'commit current unstaged work', 'clean-commit all unstaged', or 'simplify this without changing behavior.'

Project-agnostic, behavior-preserving cleanup, semantic clarity refactor, codebase slimming, and test audit pass for existing codebases. Use when Codex needs to clean up a changed area, make code leaner without product changes, reduce ambiguity in names, types, fields, status objects, or string unions, remove dead or misleading code, cut bloat and excess indirection, collapse duplicate branches, align nearby tests with the real contract, trim brittle or duplicate tests, or add focused regression coverage without broadening into product changes or architecture work. Trigger on requests like 'clean this up', 'make this leaner', 'cut bloat', 'simplify this without changing behavior', or 'remove dead code.'

Use for representation-first ownership checks on architecture-sensitive edits, state/cache/lifecycle/reconnect/sync work, render/physics/audio/shader systems, canonical path cleanup, or when the user asks who should own a behavior. Guides quantity classification, transformation tracing, deepest valid owner selection, deletion of false owners, and invariant proof.

Create repo-grounded TeX Technical Design Dossiers and companion PDFs. Use for LaTeX technical design dossiers, formal specifications, algorithm-heavy plans, and phased implementation documents.

Run public-safe SEO and GEO audits for any project using local evidence first, then optional current external evidence when available.