Run any Skill in Manus with one click

$pwd:

git-commit

Name: Git Commit
Author: nimbalyst

// 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.

Run Skill in Manus

$ git log --oneline --stat

stars:668

forks:85

updated:April 21, 2026 at 20:31

SKILL.md

readonly

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.

Git Commit Workflow in Nimbalyst

This skill is for the "Commit with AI" feature which provides an interactive commit proposal widget.

IMPORTANT: Only use this when:

The user clicks the "Commit with AI" button (you'll see a message asking you to use developer_git_commit_proposal)
The user explicitly asks for "smart commit" or "commit with AI"

Do NOT use this for:

Generic commit requests like "commit this", "commit the changes", "make a commit"
For those, use standard git commands: git add and git commit

Required Steps

Check 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 below
- reasoning: Explanation of why these files were selected

Commit Message Guidelines

Start with type prefix: feat:, fix:, refactor:, docs:, test:, chore:
Focus on IMPACT and WHY, not implementation details
Title describes user-visible outcome or bug fixed
Use bullet points (dash prefix) only for multiple distinct changes
Keep lines under 72 characters
No emojis
Lead with problem solved or capability added, not technique used

Good vs Bad Examples

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"

Important

Do NOT run git add or git commit commands directly
Do NOT add "Co-Authored-By" or attribution lines
Do NOT add marketing taglines or links
Include ALL session-edited files that have changes - the user can deselect files in the widget if needed
The widget allows users to review, edit the message, and select/deselect files before confirming

related-skills.json

same repository

feedback-intake.md

from "nimbalyst/nimbalyst"

Help 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.

2026-05-19668

excalidraw.md

from "nimbalyst/nimbalyst"

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.

2026-04-21668

extension-development.md

from "nimbalyst/nimbalyst"

Build, install, and hot-reload Nimbalyst extensions using MCP tools. Use when developing, testing, or iterating on Nimbalyst extensions.

2026-03-23668

planning.md

from "nimbalyst/nimbalyst"

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.

2026-02-26668

datamodellm.md

from "nimbalyst/nimbalyst"

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.

2026-01-29668

mockuplm.md

from "nimbalyst/nimbalyst"

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.

2026-01-29668

package.json

"author": "nimbalyst"

"repository": "nimbalyst/nimbalyst"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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.

Git Commit Workflow in Nimbalyst

This skill is for the "Commit with AI" feature which provides an interactive commit proposal widget.

IMPORTANT: Only use this when:

The user clicks the "Commit with AI" button (you'll see a message asking you to use developer_git_commit_proposal)
The user explicitly asks for "smart commit" or "commit with AI"

Do NOT use this for:

Generic commit requests like "commit this", "commit the changes", "make a commit"
For those, use standard git commands: git add and git commit

Required Steps

Check 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 below
- reasoning: Explanation of why these files were selected

Commit Message Guidelines

Start with type prefix: feat:, fix:, refactor:, docs:, test:, chore:
Focus on IMPACT and WHY, not implementation details
Title describes user-visible outcome or bug fixed
Use bullet points (dash prefix) only for multiple distinct changes
Keep lines under 72 characters
No emojis
Lead with problem solved or capability added, not technique used

Good vs Bad Examples

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"

Important

Do NOT run git add or git commit commands directly
Do NOT add "Co-Authored-By" or attribution lines
Do NOT add marketing taglines or links
Include ALL session-edited files that have changes - the user can deselect files in the widget if needed
The widget allows users to review, edit the message, and select/deselect files before confirming

git-commit

Git Commit Workflow in Nimbalyst

Required Steps

Commit Message Guidelines

Good vs Bad Examples

Important

More from this repository

More from this repository

Git Commit Workflow in Nimbalyst

Required Steps

Commit Message Guidelines

Good vs Bad Examples

Important