Menu
Commit uncommitted changes with clear commit messages. Use when the user asks to commit changes, save work, or create a commit.
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
Run affected tests, typecheck, and lint (with autofix) to catch CI failures locally before pushing. Use when CI is failing or before pushing to avoid CI failures. Offers to fix typecheck/test failures and to amend+push when clean.
Create a GitHub PR for the current branch with auto-generated description. Use when the user asks to create a pull request, open a PR, or put up changes for review.
Create a Linear ticket for the current branch on the One Big Team, auto-assigning the appropriate Linear project and team/product labels based on which part of the codebase changed. Use when the user asks to create a Linear ticket, file a Linear issue, or track work in Linear for changes on the current branch.
Render, read, and add component examples in the examples renderer. Files take two forms — colocated `*.examples.tsx` (e.g. `Checkbox.examples.tsx` next to `Checkbox.tsx`) or grouped `examples/*.tsx` (e.g. `Checkbox/examples/Default.tsx`). Covers exact iframe URLs per example, story-id derivation, multi-worktree-aware server discovery, file conventions, and the onboarding gate. Onboarded products (the authoritative validation list — only invoke this skill when the work touches one of these): `apps/staff/`. Verify at runtime with `nx show projects --with-target examples`. Use to render, screenshot, inspect, or extend an example in an onboarded product. For anything outside the onboarded list, this skill does not apply.
Create a Storybook story for a component. Use when the user asks to add a story, write a story, or create a Storybook story for a component.
Go through a PR's review comments one by one, propose solutions, and commit fixes. Use when the user wants to address PR feedback, review comments, or resolve PR review requests.
| name | commit |
| description | Commit uncommitted changes with clear commit messages. Use when the user asks to commit changes, save work, or create a commit. |
This skill commits uncommitted changes with clear, descriptive commit messages.
Run these commands to understand what needs to be committed:
git status
git diff HEAD --stat
git diff HEAD
Read any modified files if needed to understand the context of changes.
If on main:
Prompt the user to create a new branch. Suggest a name based on the changes.
Check if GitChildBranchHelpers is installed:
ls .git/child_branch_helper/ 2>/dev/null
If the directory exists, use cmk (child make branch):
cmk <username>/<short-description>
Otherwise, use regular git:
git checkout -b <username>/<short-description>
Branch naming convention: <username>/<kebab-case-description>
If not on main:
Important: Ask the user if they want to commit to the current branch or create a new one. If the user explicitly says "commit to the current branch", skip this prompt.
Stage all relevant changes:
git add <files>
CRITICAL: Do NOT stage files that contain secrets (.env, credentials.json, etc.)
Create a commit message following this format:
[Component][STATE_CODE] Brief descriptionExamples:
[Workflows][US_IX] Custom Tab - Full Term Discharge tool[Public Pathways][US_NY] Accessibility audit fixes[Meetings] Add staff member's email to meeting details UI[US_TN] Add "Bi-Annual/Other" as a 3rd FE-only oppgit commit -m "$(cat <<'EOF'
<commit message>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
After committing, tell the user:
✓ Created commit on branch: <branch-name>
Commit: <commit-hash-short>
<commit message title>
Files committed:
- <file1>
- <file2>
If you need to make changes:
- Undo commit (keep changes): git reset --soft HEAD~1
- Amend commit message: git commit --amend -m "New message"
- Rename branch: git branch -m <new-name>
Ask the user if they want to push. If yes:
Check if branch has upstream:
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
If the branch already has an upstream (command succeeds):
git push
If the branch is new (command fails):
git push -u origin <branch-name>