// Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.
| name | git-commit |
| description | Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead. |
This skill is for the "Commit with AI" feature which provides an interactive commit proposal widget.
IMPORTANT: Only use this when:
Do NOT use this for:
git add and git commitCheck if file context is already provided in the prompt
When the user clicks "Commit with AI", the prompt includes a pre-fetched list of session-edited files with uncommitted changes. If you see a file list in the prompt (lines like - path/to/file.ts (modified)), skip step 2 and go directly to step 3 using those files.
Get session-edited files (fallback only)
Only if no file list was provided in the prompt:
Call mcp__nimbalyst-mcp__get_session_edited_files to get ALL files you edited during this AI session, then cross-reference with git status.
Propose the commit
Call mcp__nimbalyst-mcp__developer_git_commit_proposal with:
filesToStage: ALL session-edited files that have changes (do not cherry-pick a subset)commitMessage: A well-crafted commit message following the guidelines belowreasoning: Explanation of why these files were selectedfeat:, fix:, refactor:, docs:, test:, chore: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"
git add or git commit commands directlyHelp the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.
Create diagrams and visual drawings using Excalidraw (.excalidraw files). Use when the user wants flowcharts, architecture diagrams, system diagrams, sketches, or any visual diagram. For database schemas and entity relationship diagrams, use the DataModelLM extension instead.
Build, install, and hot-reload Nimbalyst extensions using MCP tools. Use when developing, testing, or iterating on Nimbalyst extensions.
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.
Create visual data models for database schemas using Nimbalyst's DataModelLM editor. Use when the user wants to design a data model, database schema, entity relationship diagram, or Prisma schema.
Create visual UX mockups using HTML/CSS files (.mockup.html). Use when the user wants to design UI, wireframes, visual layouts, or plan features visually.