create-commit

Create Git commits with imperative subject lines and descriptive bodies.

Updated Jan 4, 2025
One-click install
npx skills add https://github.com/dreamtides/dreamtides --skill create-commit-dreamtides
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-commit
Source: https://github.com/dreamtides/dreamtides/tree/main/.llms/skills/create-commit
Command: npx skills add https://github.com/dreamtides/dreamtides --skill create-commit-dreamtides

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create clear, concise, and informative Git commits for your completed work, ensuring your version history is well-documented and easy to understand.

Core Features & Use Cases

  • Review Changes: Provides steps to thoroughly review all modified files before committing.
  • Craft Effective Messages: Guides you in writing imperative subject lines and descriptive bodies for your commit messages.
  • Stage Files: Ensures relevant files are staged correctly using git add.
  • Use Case: After finishing a feature or bug fix, use this Skill to ensure your commit message accurately reflects the changes made and the reasoning behind them, making collaboration smoother.

Quick Start

Use the create-commit skill to stage all changes and create a commit with a summary of your work.

Frequently Asked Questions about create-commit

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

FAQPage Schema
How do I write a clear git commit message for my code changes?

To write a clear git commit message, use an imperative subject line followed by a descriptive body that references affected components and explains the reasoning behind the changes. This ensures your version control history remains clean and informative for collaboration.

What is the best way to stage files before creating a git commit?

The best way to stage files before creating a git commit is to thoroughly review all modified files first, then use git add to stage relevant files. This ensures only intended code changes are included in the commit staging area.

How do I review staged and unstaged changes before committing?

You can review staged and unstaged changes by examining all modified files before committing. This review process helps identify affected components and guides the staging of relevant files to ensure an accurate version control history.

Does this git commit skill work for both feature development and bug fixes?

Yes, this git commit skill works for both feature development and bug fixes. It guides you through staging relevant files and writing imperative commit messages that accurately summarize completed work regardless of the task type.

Why should I use imperative mood in git commit subject lines?

You should use imperative mood in git commit subject lines because it provides clear, concise instructions on what the commit does. This practice maintains a well-documented version control history that is easy to understand during software development.