/commit
Create a git commit with concise, bullet-point commit message
$ npx -y skills add nimbalyst/nimbalyst --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/commit
Context preview
What this command does when you run it.
Create a git commit with concise, bullet-point commit message
Command definition
commit.mdname: commit
description: Create a git commit with concise, bullet-point commit message
Prepare a git commit following these steps:
1. Run `git status` and `git diff` to see changes 2. Review recent commits (`git log --oneline -5`) to match the style 3. Draft a concise commit message:
- Start with type prefix: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `chore:`
- **Focus on IMPACT and WHY, not implementation details**
- The title should describe the user-visible outcome or bug fixed
- Use bullet points (dash prefix) only if there are multiple distinct changes
- Keep each line under 72 characters
- No emojis
4. Run the `developer_git_commit_proposal` tool to propose the commit to the user
- Do NOT run `git add` - the widget handles staging when the user confirms
**Commit Message Guidelines:**
- Lead with the problem solved or capability added, not the technique used
- BAD: "feat: add pre-edit tagging for non-agentic AI providers"
- GOOD: "fix: OpenAI/LMStudio diffs now persist across app restarts"
- BAD: "refactor: extract helper function for validation"
- GOOD: "fix: prevent crash when user input is empty"
- The body can explain HOW if it's non-obvious, but title = IMPACT
**Issue Linking (for auto-close):**
- If the commit is intended to resolve a referenced issue or tracker item,
include the tracker reference on its own line in the proposed message
- Prefer that system's canonical closing syntax, such as `Fixes #123`,
`Closes ABC-123`, or similar
- This applies to local Nimbalyst tracker items too, not just GitHub issues:
a session-linked item closes on `Fixes NIM-123` and the session is marked complete. Omitting it strands the finished item in `in-review`
- Use a neutral reference (`Refs ABC-123`) only when the commit does NOT
finish the item — a work-in-progress commit should not close it
**Important:**
- Do NOT add "Co-Authored-By" or any attribution lines
- Do NOT add marketing taglines or links
- Be direct and factual
- Keep it brief - avoid unnecessary details about what wasn't changed
Read more
name: commit description: Create a git commit with concise, bullet-point commit message
Prepare a git commit following these steps:
1. Run `git status` and `git diff` to see changes 2. Review recent commits (`git log --oneline -5`) to match the style 3. Draft a concise commit message:
- Start with type prefix: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `chore:`
- **Focus on IMPACT and WHY, not implementation details**
- The title should describe the user-visible outcome or bug fixed
- Use bullet points (dash prefix) only if there are multiple distinct changes
- Keep each line under 72 characters
- No emojis
4. Run the `developer_git_commit_proposal` tool to propose the commit to the user
- Do NOT run `git add` - the widget handles staging when the user confirms
**Commit Message Guidelines:**
- Lead with the problem solved or capability added, not the technique used
- BAD: "feat: add pre-edit tagging for non-agentic AI providers"
- GOOD: "fix: OpenAI/LMStudio diffs now persist across app restarts"
- BAD: "refactor: extract helper function for validation"
- GOOD: "fix: prevent crash when user input is empty"
- The body can explain HOW if it's non-obvious, but title = IMPACT
**Issue Linking (for auto-close):**
- If the commit is intended to resolve a referenced issue or tracker item,
include the tracker reference on its own line in the proposed message
- Prefer that system's canonical closing syntax, such as `Fixes #123`,
`Closes ABC-123`, or similar
- This applies to local Nimbalyst tracker items too, not just GitHub issues:
a session-linked item closes on `Fixes NIM-123` and the session is marked complete. Omitting it strands the finished item in `in-review`
- Use a neutral reference (`Refs ABC-123`) only when the commit does NOT
finish the item — a work-in-progress commit should not close it
**Important:**
- Do NOT add "Co-Authored-By" or any attribution lines
- Do NOT add marketing taglines or links
- Be direct and factual
- Keep it brief - avoid unnecessary details about what wasn't changed
Nimbalyst is a free, open-source, local, interactive visual editor & session/task manager for developers, product managers, designers, builders.
Repo: nimbalyst/nimbalyst
Other commands on nimbalyst.
- /android-release
Prepare and execute an Android release (patch/minor/major)
Open command - /bug-report
Gather details and draft an actionable bug report for developers.
Open command - /design
Create a new plan document for tracking work.
Open command - /e2e-devcontainer
Run E2E tests in a dev container (isolated environment)
Open command - /implement
Execute a plan document while keeping progress synchronized.
Open command - /investigate-performance
Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evidence before proposing a fix.
Open command

