commit
/commit
Create git commits in spaces/[project]/ with quality checks and conventional message formatting.
Usage
/commit yourbench # Interactive commit
/commit yourbench "feat: add auth" # Direct with message
/commit coordinatr --amend # Amend last commit (safety checks)
/commit yourbench "fix: typo" --no-verify # Skip hooks
Two Repos Involved
Meta-repo (ideas/): spaces/yourbench/
├── ideas/yourbench/ ├── src/
│ ├── specs/ ├── tests/
│ └── issues/ └── .git/ <- Project git
├── .claude/
└── .git/ <- Meta-repo git
Auto-detect behavior:
- Only
spaces/[project]/changed -> commit in project repo - Only
ideas/or meta-repo changed -> commit in meta-repo - Both changed -> ask: "Commit to both repos? (project/meta/both)"
Execution Flow
1. Detect Changes
# Check meta-repo
git status --porcelain ideas/ .claude/ shared/ resources/
# Check project repo
git -C spaces/[project] status --porcelain
2. Run Quality Checks (unless --no-verify)
npm test # or pytest, cargo test, etc.
npm run lint
3. Review Changes
git status
git diff --staged
4. Generate Commit Message
Conventional commit format:
type(scope): description
[optional body]
Co-Authored-By: Claude <noreply@anthropic.com>
Types:
feat: New featurefix: Bug fixdocs: Documentationrefactor: Code refactoringtest: Adding/updating testschore: Maintenance
Auto-detect type from changes:
- New files in
src/->feat - Changes to existing behavior ->
fixorrefactor - Only test files ->
test - Only docs ->
docs
5. Link to Issue (if applicable)
If on feature branch like feature/001-auth:
feat(001): implement user authentication
Refs: TASK-001
6. Execute Commit
cd spaces/yourbench
git add .
git commit -m "message..."
Amend Mode
Safety checks before amending:
- Not pushed to remote:
git log @{u}..HEAD - You're the author:
git log -1 --format='%ae'
Branch-Aware Messages
| Branch | Commit Type |
|---|---|
feature/001-auth |
feat(001): ... |
bugfix/002-login |
fix(002): ... |
main / develop |
No issue reference |
Error Handling
| Error | Resolution |
|---|---|
| Project not found | Check spaces/[project]/ exists |
| Not a git repo | Run git init in project |
| Tests failing | Fix tests before committing |
| Nothing to commit | No staged/unstaged changes |
| Amend pushed commit | Cannot amend, create new commit |
More from taylorhuston/local-life-manager
daily-review
Complete daily journal review. Use at end of day or next morning to fill in journal sections, review highlights, and plan tomorrow. Triggers on "daily review", "end of day", "journal review", "what did I do today".
48weekly-review
Weekly review and planning session. Use at end of week or weekend to review progress, plan next week, and set priorities. Triggers on "weekly review", "plan my week", "what did I do this week", "Sunday planning".
25daily-journal
Daily journal management for the my-vault Obsidian vault. Use for morning routines, daily reviews, quick journal updates, checking yesterday's entry, or setting today's highlight. Triggers on "good morning", "daily review", "journal", "what did I do", "highlight".
23life-planning
Cross-repo life and project planning. Use when user wants to plan their week, prioritize projects, review progress across all areas, or make decisions about what to focus on. Triggers on "plan my week", "what should I work on", "prioritize", "weekly review", "life planning".
23flashcards
Generate spaced repetition flashcards from notes or topics. Use when user wants to create flashcards, make review cards, prepare for spaced repetition, or convert notes to quiz format. Triggers on "flashcards", "make cards", "spaced repetition", "review cards".
21video-summarize
Summarize a single YouTube video and create a note. Use when user shares a video URL or asks to summarize a specific video. Triggers on "summarize this video", "video summary", YouTube URLs.
17