Engineering Workflow skills for Codex
Skills that shape how Codex works rather than what it builds: reproducing bugs before patching, test-driven loops, atomic commits and Conventional Commits, pull requests reviewers can approve, code review with severity labels, safe refactors, dependency upgrades, git history repair, codemods and onboarding into an unfamiliar codebase.
curl -fsSL codexskills.dev/install.sh | sh -s -- --category workflow Installs all 40 into ~/.agents/skills/. Or download the zip.
All 40 Engineering Workflow skills
Each opens the full SKILL.md, example prompts and every way to install it.
-
Biome Setup
Swap ESLint and Prettier for Biome, knowing what you lose -
Changelog Writing
Entries users can act on, not commit subjects -
Code Archaeology
Find the commit, PR and reason behind any line -
Code Comments
Keep the why, delete the what -
Code Review
Find the 3 a.m. bug before the naming nits -
Codebase Onboarding
Answer how this repo works with file paths, not guesses -
Codemods
Change 500 files with code you can rerun -
CODEOWNERS Setup
Route every PR to the team that owns the code -
Conventional Commits
Commit types your release tooling can trust -
Dead Code Removal
Delete unused code with evidence, not hope -
Dependency Upgrades
One major at a time, changelog read first -
Error Handling Patterns
Typed errors, one boundary, nothing swallowed -
ESLint Setup
Flat config that lints the files you think it does -
Feature Flags
Ship dark, roll out slowly, delete the flag after -
Git Bisect
Name the commit that broke it, in log2(n) runs -
Git Commit Hygiene
Atomic commits a reviewer can read in order -
Git History Surgery
Rewrite history with a backup and a proof -
Git Worktrees
Two branches checked out at once, no stashing -
Hotfix Process
Smallest safe fix, from the deployed tag, ported everywhere -
Implementation Planning
A plan grounded in real files, approved before coding -
Legacy Code Characterization
Pin what old code does before you touch it -
Merge Conflict Resolution
Keep both intents, not just one side's text -
Minimal Repro Cases
Shrink any bug to one file a maintainer will run -
Monorepo Tooling
Cache hits you can trust, CI that builds only what changed -
Naming Conventions
Names a reader can predict without opening the file -
Pre-commit Hooks
Hooks that fix staged files in seconds, not minutes -
Pull Request Writing
PR descriptions reviewers can approve fast -
Regex Crafting
Regexes with test tables and no catastrophic backtracking -
Release Management
Tag the tested commit and write rollback first -
Review Feedback Response
Close every thread, open no new ones -
Root Cause Analysis
Five whys that branch, and actions that bite -
Ruff Setup
One pinned Ruff in place of flake8, Black and isort -
Safe Refactoring
Small green steps, zero behaviour change -
Semantic Versioning
Major, minor or patch, decided against the real API -
Spec to Code
Every requirement traced to code and a test -
Stacked Pull Requests
Small dependent PRs that merge bottom-up cleanly -
Systematic Debugging
Explain the bug before you change a line -
Technical Debt Triage
Rank debt by the interest it charges every month -
Test-Driven Development
See it fail for the right reason, then pass -
Trunk-Based Development
Merge daily, keep main releasable, revert first
No Engineering Workflow skill matches that.
Where to start
Install the ones that match requests you make every week. Name one with $code-review when you want it for sure; otherwise Codex picks by description.
Start with
- Code ReviewFind the 3 a.m. bug before the naming nits
- Error Handling PatternsTyped errors, one boundary, nothing swallowed
- ESLint SetupFlat config that lints the files you think it does
Install a few by name
curl -fsSL codexskills.dev/install.sh | sh -s -- biome-setup changelog-writing 104-line POSIX script. No sudo, no telemetry. Read install.sh
By stack
In collections
Engineering Workflow FAQ
How do I install every Engineering Workflow skill at once?
Run curl -fsSL https://codexskills.dev/install.sh | sh -s -- --category workflow to put all 40 in ~/.agents/skills/, or add --project to install them into the current repository's .agents/skills/. You can also download the category zip and unpack it yourself.
Does installing 40 skills slow Codex down?
Hardly. At startup Codex sees only each skill's name and description, a few dozen words apiece, and reads a full SKILL.md only when a task needs it. Install the whole category if the work fits; unused skills cost almost nothing.
Which Engineering Workflow skill should I start with?
Start with Code Review, Error Handling Patterns, ESLint Setup. They cover the requests that come up most in this category. Mention one with $code-review to try it.