commit

Stage all Git changes and generate a descriptive commit message.

862|67|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/saffron-health/libretto --skill commit-saffron-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/saffron-health/libretto/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/saffron-health/libretto --skill commit-saffron-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of staging all current code changes and creating a Git commit with a descriptive message, streamlining the version control workflow.

Core Features & Use Cases

  • Automated Staging: Stages all modified and new files in the repository.
  • Intelligent Commit Messaging: Analyzes code changes to generate a conventional commit message.
  • Change Summarization: Displays a summary of staged changes and the final commit details.
  • Use Case: After implementing a new feature and fixing a bug, use this Skill to quickly stage all related files and create a commit like feat: implement user authentication and fix login bug.

Quick Start

Use the commit skill to stage all changes and create a git commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I stage all code changes and generate a git commit message automatically?

To stage all code changes and generate a git commit message automatically, you can use an automated version control workflow that analyzes modified files and creates a descriptive, conventional commit message summarizing the code changes.

How does intelligent commit message generation work for code changes?

Intelligent commit message generation works by analyzing your staged code changes to understand the context of modifications, then synthesizing a descriptive, conventional commit message that accurately reflects the implemented features or bug fixes.

Do I need Git CLI installed to stage and commit code changes through automation?

Yes, you need Git CLI installed and configured for repository operations before using automated staging and commit message generation, as the underlying version control workflow relies directly on Git CLI commands to process code changes.

Can I summarize staged changes before finalizing a git commit?

Yes, you can summarize staged changes before finalizing a git commit. The version control workflow displays a summary of staged code changes and the final commit details, ensuring you understand the modifications before the commit is applied.

What's the best way to create conventional commit messages for multiple file updates?

The best way to create conventional commit messages for multiple file updates is to stage all modified files at once and use an automated code analysis tool to generate a single, descriptive commit message covering all related code changes.

Why should I use automated code staging instead of manual git add for version control?

You should use automated code staging instead of manual git add because it streamlines your development workflow by instantly staging all modified and new files in the repository and generating a descriptive commit message, reducing manual version control overhead.