Menu
Write a commit message following the project template and save it to commit.msg
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
Create a GitHub issue from a summary description. Drafts the title and body, shows a preview, and asks for confirmation before publishing.
Thorough peer code review of a PR or branch — correctness, bugs, logic errors, edge cases, code quality, simplicity, naming, test coverage. Takes a PR number or base branch argument. Pulls PR metadata via gh if available.
Autonomous Quint formal specification workflow — generate specs (new or from codebase), typecheck, create witnesses, run invariants, and verify. Like plan mode but for formal specs.
Merge a branch into the current branch — detect conflicts, summarize them, and resolve them automatically where possible. Asks the user when unsure which changes to keep.
Verify documentation (README, runbooks, module docs) aligns with the actual codebase and fix any drift
Generate a PR summary from all commits since the branch diverged from a given parent branch, written to pr-summary.msg
| name | commit |
| description | Write a commit message following the project template and save it to commit.msg |
| allowed-tools | Bash, Read, Grep, Glob |
Examine changes and write a commit message to commit.msg following the project's commit message template.
rm -f commit.msg
ensure commit.msg is in the .gitignore in root of repo:
if [ ! -f .gitignore ] || ! grep -qF "commit.msg" .gitignore; then
echo "commit.msg" >> .gitignore
fi
Run these commands to understand what's being committed:
git status
git diff
git diff --cached
git log --oneline -10
Look at both staged and unstaged changes. Read changed files for context if needed.
Write the commit message to commit.msg using this template:
[First line gives a top level commit message in 100 chars or less]
## Problems to Solve
[What problems is this commit trying to solve?]
## Plan
[What will you work on this iteration? Why?]
## Work Log
[Fill this in as you work]
## Summary
[Fill this in before committing. Give an overview of what you accomplished, or to pass forward context and priorities if there is still work to do on your current task.]
Guidelines:
Once you have written the commit message, you can stage your changes and commit using the message from commit.msg, then push to the remote repository:
git add .
git commit -F commit.msg
git push