commit

Generate Git commit messages for staged changes with bulleted summaries.

Updated Mar 10, 2024
One-click install
npx skills add https://github.com/Mjvolk3/Swanki --skill commit-mjvolk3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Mjvolk3/Swanki/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Mjvolk3/Swanki --skill commit-mjvolk3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of committing staged changes in a Git repository by generating a descriptive commit message, streamlining the development workflow.

Core Features & Use Cases

  • Auto-generated Commit Messages: Creates clear, concise, and bulleted commit messages based on staged changes.
  • Style Consistency: Analyzes existing commit history to match the repository's message style.
  • Use Case: After making several code modifications, you can use this Skill to commit them with a well-formatted message that summarizes the changes, ensuring consistency and clarity in your project's history.

Quick Start

Use the commit skill to commit your staged changes with an auto-generated message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate Git commit messages automatically?

You can generate Git commit messages automatically by using a tool that analyzes your staged changes and repository history to create a summary line and a bulleted list of modifications.

How do I match my new Git commit message to my repository's style?

To match your repository's style, the generation process analyzes existing commit log history to ensure the new auto-generated message adheres to the established formatting and best practices.

Can I automate committing staged changes with a bulleted list of modifications?

Yes, you can automate committing staged changes by generating a descriptive commit message that includes a summary line and a bulleted list of changes, ensuring clarity and consistency.

Does the auto-generated commit message include co-authorship information?

Yes, the generated commit message includes a Co-authored-by line to ensure proper attribution alongside the summary line and the bulleted list of staged changes.

What is the best way to write consistent Git commit messages for code modifications?

The best way to write consistent Git commit messages is to analyze repository log history and auto-generate a summary with a bulleted list of changes, ensuring adherence to best practices.

Do I need to stage my code changes before auto-generating a commit message?

Yes, you must stage your code changes first, as the commit message generation analyzes the currently staged changes in your Git repository to create the descriptive summary.