skills.rest
segersniels
segersnielsCOMMUNITY
Explore all skills by this author →
Website𝕏@segersniels_GitHub

create-commit

Create conventional Git commits from staged changes with scoped messages.

Updated Dec 27, 2018
Search Tags:#git#workflow#commit#atomic-commits#version-control#conventional-commits
One-click install
npx skills add https://github.com/segersniels/dotfiles --skill create-commit-segersniels
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-commit
Source: https://github.com/segersniels/dotfiles/tree/main/.opencode/skill/create-commit
Command: npx skills add https://github.com/segersniels/dotfiles --skill create-commit-segersniels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline and standardize your Git workflow by creating clear, atomic commits with well-defined scope on user request.

Core Features & Use Cases

  • Enforces conventional commit messages to improve traceability and reviewability.
  • Guides users to create small, focused commits rather than a single large change.
  • Supports typical development scenarios including feature work, bug fixes, and dependency updates.

Quick Start

Use this skill to create a well-scoped commit with a concise description for your current changes.

Frequently Asked Questions about create-commit

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

FAQPage Schema
How do I create atomic Git commits using conventional commit formatting?▼

Atomic Git commits are created by verifying staged changes and applying conventional commit formatting to ensure each commit is well-scoped and focused. This approach enforces clear, traceable commit messages for features, bug fixes, or documentation updates.

What is the best way to automate writing focused Git commit messages?▼

Automating focused Git commit messages involves guiding the user to craft targeted descriptions based on verified staged changes. This standardizes your version control workflow by enforcing small, meaningful commits rather than a single large change.

When do I need to use conventional commits in my version control workflow?▼

Conventional commits are needed in a version control workflow to improve traceability and reviewability. You should use this format for daily development scenarios including feature work, bug fixes, and dependency updates to maintain a clear project history.

How do I split a large staged change into smaller, well-scoped commits?▼

Splitting large staged changes into smaller commits requires verifying the staged changes first, then guiding the development workflow to create focused, atomic commits. This ensures each commit represents a single logical change with a concise description.

Does this Git commit workflow support dependency updates and documentation changes?▼

This Git commit workflow supports dependency updates and documentation changes alongside feature work and bug fixes. It applies conventional commit formatting to these daily development scenarios to maintain consistent, traceable version control history.

Related Skills

Explore More Software Engineering Skills→
gihwan-devgihwan-dev
1

commit

Generate conventional commit messages for staged and unstaged Git changes.

Community
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
ionmidoriionmidori

Git Agentic Workflows

Define Git protocols for atomic commits and conventional messages.

Community
Intermediate
thesammykinsthesammykins

git-master

Enforce atomic commits, controlled rebases, and precise history searches.

Community
Advanced