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
Investigate a stable counts validation failure for a state supervision or incarceration period table by identifying which fields changed and why. Use when a stable counts validation is failing or has recently failed for a state entity (e.g. "why is the NC stable counts failing", "investigate stable counts for US_ID supervision periods", "dig into the stable counts failure for supervision periods").
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.
Investigate a GitHub bug ticket by fetching PII from the go/github-pii doc and suggesting BQ investigation queries.
Post a validation comment to a GitHub PR or issue using the standard format. Use when the user asks to post a comment to a PR or issue, post sandbox or ingest validation results, share validation findings on a PR or ticket, or anything similar that involves posting validation results as a GitHub comment.
Add a new field to opportunity configs in the workflows admin panel. Use when asked to add a new config field, property, or attribute to the workflows opportunity configuration system.
Use this skill when a user wants to structure BigQuery views into the standard Pollen view pattern. All Pollen analysis is in the research/notebooks/policy folder -- do not apply this skill outside that folder. Triggers include: "structure my views", "create view files", "pull views from my notebook", "set up the view folder structure", "make my SQL into view builders", or any request to convert notebook SQL or .sql files into the SimpleBigQueryViewBuilder pattern used by policy analysis work.
| 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:
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:
[STATE_CODE] Brief description or [Component] Brief descriptionExamples:
[US_IX] Add CRC-like bed eligibility criteria[BigQuery] Fix view dependency ordering[Workflows] Update client record supervision levelgit 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>