commit

Group git changes into logical commits with angular-style messages.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill commit-nsheaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/scm-utils/skills/commit
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill commit-nsheaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often accumulate mixed or noisy changes that make repository history hard to read and review; this Skill guides the creation of logical, focused git commits by inspecting the working tree, diffs, and recent commit patterns to propose clear commit groupings and messages.

Core Features & Use Cases

  • Guided Review Workflow: Runs git status, diffs, and recent commit history to recommend which files should be grouped together.
  • Commit Strategy & Messaging: Encourages angular-style messages (feat:, fix:, docs:, etc.) and focuses on explaining why changes were made.
  • Interactive Clarification: Prompts the user when the intent of changes or the provided hint is ambiguous, and avoids committing debug or unrelated files.
  • PR Awareness: Checks for existing pull requests and updates or aligns commit strategy with PR titles and bodies when applicable.
  • Use Case: Preparing a clean set of commits for a feature branch before opening or updating a pull request so reviewers can understand intent and scope.

Quick Start

Commit the current outstanding changes into logical, focused commits guided by the hint "commit only documentation and formatting" and ask me before committing any unclear edits.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split mixed git changes into focused commits?

Split mixed git changes into focused commits by analyzing git status and diffs to group related files, then generating angular-style commit messages for each logical change set.

How does automated git commit message generation work?

Automated git commit message generation works by reviewing recent commit patterns and current diffs to craft angular-style messages that explain why changes were made.

What is the best way to prepare a clean git history for a pull request?

Prepare a clean git history for a pull request by grouping related file changes into logical commits, aligning commit messages with PR titles, and avoiding unrelated debug files.

Can I automate git commits and still align them with existing pull request metadata?

Yes, you can automate git commits and align them with existing pull request metadata by checking open PRs and updating commit strategy to match the PR titles and bodies.

Does the commit automation commit debug or unrelated files automatically?

No, the commit automation avoids committing debug or unrelated files by prompting for clarification when the intent of changes or provided hints is ambiguous.