Menu
Create a git commit following this repo's conventions. Use when the user asks to commit changes (e.g. "commit", "commit this", "/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
| name | commit |
| description | Create a git commit following this repo's conventions. Use when the user asks to commit changes (e.g. "commit", "commit this", "/commit"). |
Create a git commit that follows this repo's conventions.
docs/harness/vcs/commits.md for the conventions. Follow them exactly.git status, git diff (staged and unstaged), and git log -5 --oneline to understand the changes and recent message style.Create a feature branch using this repo's branch-naming conventions.
Creates a new vcs branch. Should rarely be called directly.
Decompose the working tree into clean commits and open a PR. Use when the user asks to ship the current change end-to-end.
Create a commit following this repo's conventions (Conventional Commits). Use when the user asks to commit changes. Optional file list scopes the commit.
Creates a vcs commit. Should rarely be called directly.
Opens a vcs pull request. Should rarely be called directly.