Menu
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
| name | clean-commits |
| description | Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point |
Every commit is atomic, descriptive, and leaves code in a working state.
Core principle: Anyone should be able to checkout any commit and have working code.
Announce at use: "I'm committing with a descriptive message following clean-commits standards."
[type](scope): Short description (max 72 chars)
[Optional body - what and why, not how]
[Optional footer - issue references, breaking changes]
Refs: #[ISSUE_NUMBER]
| Type | Use For |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no code change |
refactor | Code restructuring |
test | Adding/fixing tests |
chore | Maintenance, dependencies |
feat(auth): Add user registration endpoint
Implement POST /api/users/register with email validation,
password hashing, and duplicate detection.
- Validates email format and uniqueness
- Hashes password with bcrypt
- Returns user object without password
Refs: #123
fix(auth): Prevent redirect loop on expired session
Session expiry was triggering redirect to login, which
checked session, found expired, and redirected again.
Now clears session cookie before redirecting.
Refs: #456
test(auth): Add integration tests for registration
Cover success case, duplicate email, invalid format,
and weak password scenarios.
Refs: #123
| Atomic | Not Atomic |
|---|---|
| One logical change | Multiple unrelated changes |
| Passes all tests | Breaks tests |
| Complete feature slice | Half-implemented feature |
| Can be reverted cleanly | Reverts would break things |
If you have multiple changes, commit them separately:
# Stage specific files
git add src/auth/register.ts
git add src/auth/register.test.ts
git commit -m "feat(auth): Add registration endpoint"
# Stage next logical unit
git add src/auth/login.ts
git add src/auth/login.test.ts
git commit -m "feat(auth): Add login endpoint"
Every commit must leave the codebase in a state where:
Before committing:
# Run tests
pnpm test
# Check build
pnpm build
# Check types
pnpm typecheck
# Check lint
pnpm lint
If any fail, fix before committing.
| Too Infrequent | Just Right |
|---|---|
| "Implement entire feature" | "Add user model" |
| "Fix all bugs" | "Fix session expiry redirect" |
| "Update everything" | "Update auth dependencies" |
Smaller commits are:
# Review what changed
git diff
# Stage specific files
git add [specific files]
# Or stage interactively
git add -p
# See what will be committed
git diff --staged
# Short message (if simple)
git commit -m "fix(auth): Handle null user in session check"
# Long message (if complex)
git commit
# Opens editor for full message
# Check commit looks right
git show --stat
# Verify tests still pass
pnpm test
When to include a body:
refactor(api): Extract validation middleware
Validation logic was duplicated across 12 endpoints.
Extracted to reusable middleware that can be composed.
Alternative considered: validation library.
Rejected because our rules are domain-specific.
fix(data): Use optimistic locking for updates
Race condition was causing lost updates when two users
edited the same record simultaneously.
BREAKING CHANGE: Update operations now require
version field in request body.
Always reference the issue:
# In commit message
Refs: #123
# Or if commit closes the issue
Closes: #123
# Amend last commit (before push only!)
git add forgotten-file.ts
git commit --amend
If a commit was wrong:
# Create a new commit that undoes the change
git revert [commit-sha]
# DON'T rewrite history on shared branches
# DON'T force push to fix mistakes
Before each commit:
This skill is called by:
issue-driven-development - Throughout developmentpr-creation - Before creating PRThis skill enforces: