commit

Creates structured conventional commits with granular patch staging and GitHub CLI support.

Updated Oct 15, 2021
One-click install
npx skills add https://github.com/toqoz/config --skill commit-toqoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/toqoz/config/tree/main/home/agents/skills/commit
Command: npx skills add https://github.com/toqoz/config --skill commit-toqoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent, poorly documented, or overly broad git commits by enforcing a structured, logical, and conventional commit workflow.

Core Features & Use Cases

  • Conventional Commits: Automatically enforces the Conventional Commits specification for consistent history.
  • Patch Surgery: Enables granular staging of changes at the hunk level, ensuring each commit is atomic and revertable.
  • Safety Guards: Prevents accidental commits to protected branches like main or production.
  • Use Case: When you have multiple unrelated changes in your working directory, use this skill to split them into distinct, well-described commits that explain the motivation behind each change.

Quick Start

Ask the agent to commit the current changes using the conventional commit format and include a detailed description of the work performed.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits for multiple unrelated changes in git?

To create conventional commits for multiple changes, this skill performs patch surgery on staged changes to maintain logical separation. It splits unrelated working directory modifications into distinct, atomic, and well-described commits using the Conventional Commits specification.

What is patch surgery in git version control?

Patch surgery in git version control is the granular staging of changes at the hunk level. This process ensures each commit remains atomic and revertable by separating unrelated modifications in your working directory into logically distinct commits.

Can I automatically push commits and create pull requests with the GitHub CLI?

Yes, you can automatically push commits and create pull requests using the GitHub CLI. This skill supports optional automated pushing and pull request creation immediately after structuring your conventional git commits.

How do I prevent accidental commits to protected git branches like main?

To prevent accidental commits to protected git branches like main, this skill includes built-in safety guards. It validates branch safety before committing, ensuring structured conventional commits never accidentally target protected production branches.

Does this git workflow tool require any external dependencies?

No, this git workflow tool requires no external dependencies to structure conventional commits. However, optional automated pushing and pull request creation require the GitHub CLI to be installed in your environment.

When do I need to use the Conventional Commits specification?

You need to use the Conventional Commits specification when you require a clear and maintainable project history. It solves the problem of inconsistent or poorly documented git commits by enforcing a structured, logical commit workflow.