commit

Generates git commits with user-approved messages and staged files.

8|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill commit-scooter-lacroix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/meta/commit
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill commit-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of Git commits, ensuring clear, descriptive messages and proper staging of changes without AI attribution.

Core Features & Use Cases

  • Automated Commit Generation: Creates Git commits based on reviewed changes.
  • User Approval Workflow: Presents proposed commits for user confirmation before execution.
  • Reasoning Capture: Automatically generates reasoning files for each commit to preserve context.
  • Use Case: After implementing a new feature, use this Skill to stage, commit, and document your changes clearly and efficiently.

Quick Start

Use the commit skill to create a git commit for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits with descriptive messages?

Automating git commits involves staging changes and generating descriptive messages to preserve version control history. This Skill automates staging, commits, and reasoning file generation, presenting proposed commits for user approval before execution to ensure clear development workflow documentation.

Can I generate git commits without adding AI attribution to the message?

Yes, generating git commits without AI attribution is supported. This Skill creates commits with user-approved messages and staged files while ensuring no AI attribution is added, keeping your version control history clean and authentic to human authorship.

What is the best way to create atomic commits with clear reasoning context?

Creating atomic commits with reasoning context is achieved by generating separate reasoning files for each commit. This Skill supports atomic commits and descriptive messaging, automatically capturing the reasoning behind development changes to maintain clear version control history.

How does the user approval workflow work for automated git commits?

The user approval workflow for automated git commits presents proposed commit messages and staged files for confirmation before execution. This Skill ensures you review and approve the generated commit details, preventing unintended changes from being committed to your version control repository.

Do I need to manually stage files before using an automated commit tool?

No, manual staging is not required as a prerequisite. This Skill automates the process of staging changes, generating commit messages, and creating reasoning files, handling the full development workflow from reviewing changes to executing the final git commit.