sd-commit

Automates git commits with Conventional Commits and configurable staging.

2|2|Updated Jul 10, 2024
One-click install
npx skills add https://github.com/kslhunter/simplysm --skill sd-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sd-commit
Source: https://github.com/kslhunter/simplysm/tree/main/.claude/skills/sd-commit
Command: npx skills add https://github.com/kslhunter/simplysm --skill sd-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of git commits with a conventional message format, and can stage changes automatically or selectively to streamline your version-control workflow.

Core Features & Use Cases

  • Automatic staging modes: choose to stage all changes or only specific files before committing.
  • Conventional commit messages: enforces a standard type and scope in commit messages for consistency.
  • Workflow flexibility: supports typical development scenarios from small fixes to large feature commits.

Quick Start

Tell it to commit your changes by choosing the default mode or by specifying the exact files to stage before committing.

Frequently Asked Questions about sd-commit

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

FAQPage Schema
How do I automate git commits with conventional commit messages?

You can automate git commits with conventional commit messages by using a shell environment to apply standard type and scope formatting to your changes automatically. This enforces consistent commit messages across your development workflow.

Can I stage specific files selectively before creating a conventional commit?

Yes, you can stage specific files selectively before creating a conventional commit by specifying the exact files to stage. This selective staging mode allows controlled change sets alongside strict commit message formatting.

What is the conventional commits format and why use it for git workflow automation?

The conventional commits format enforces a standard type and scope in commit messages to maintain consistency across project history. Using it for git workflow automation streamlines version-control and ensures readable, structured commit logs for development scenarios.

Do I need a specific shell environment to automate conventional commits?

Yes, you need a shell environment with git installed to automate conventional commits. This environment supports both staging all changes and selective file staging while enforcing strict commit message formatting.

Can I stage all changes automatically before formatting a conventional commit?

Yes, you can stage all changes automatically using the 'all' mode before formatting a conventional commit. This mode handles staging of changes as configured and applies strict commit message formatting for your software development workflow.

What is the best way to enforce strict commit message formatting in git?

The best way to enforce strict commit message formatting in git is to automate the creation of conventional commits. This approach applies a standard type and scope to messages, ensuring consistency from small fixes to large feature commits.