Menu
Create a git 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 | chunk-commit |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*) |
| description | Create a git commit |
git statusgit diff HEADgit branch --show-currentgit log --oneline -10ve chunk list --current 2>/dev/null || ve chunk list --last-active 2>/dev/null || echo "(no active chunk)"Based on the above changes, create a single git commit. Use the conventional commit message format.
These files are primary work artifacts and MUST be committed:
Chunk documentation (docs/chunks/<chunk_name>/):
GOAL.md - Including status updates (FUTURE → IMPLEMENTING → ACTIVE)PLAN.md - The implementation plan with any deviations notedSource code changes (src/, tests/, etc.):
Project documentation updates:
docs/trunk/ files (DECISIONS.md, SPEC.md, etc.)Do not commit these ephemeral files:
.idea/, .vscode/ unless project-wide).ve/ (orchestrator runtime state)Use conventional commits. The message should describe what was accomplished, not just list files changed. Include the chunk context when relevant.
Example:
feat: add user authentication middleware
Implement JWT-based auth for API endpoints with refresh token support.
Update chunk status to ACTIVE with code references.
Co-Authored-By: Claude <assistant>
Collaboratively refine a high-level ambition into a set of chunk prompts.
Migrate the project's ACTIVE chunks to the present-tense, intent-owning standard. Audits each chunk's goal against the code it claims to govern; rewrites retrospective framing inline; logs over-claims that need operator triage; historicalizes chunks with no enduring intent. Designed for full-corpus migrations — fans out across many parallel sub-agents at 5 chunks per agent.
Create a new chunk of work and refine its goal. Use when the operator wants to start new intent-bearing work, chunk something, define a piece of work, or break work into a chunk.
Update code references in the current chunk and move both the PLAN.md and the GOAL.md to the ACTIVE state.
Wake an entity by loading its identity, memories, and operational context
Set up a project steward via interactive interview