skills.rest
mysticfall
mysticfallCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Coordinates atomic Git commits by reviewing, staging, and confirming before commit.

1|Updated Sep 15, 2024
Search Tags:#git#workflow#commits#review#atomic-commits#version-control#commit-message
One-click install
npx skills add https://github.com/mysticfall/alleycat --skill git-commit-mysticfall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mysticfall/alleycat/tree/main/.opencode/skills/git-commit
Command: npx skills add https://github.com/mysticfall/alleycat --skill git-commit-mysticfall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers enforce a safe, atomic Git commit workflow by guiding users to review changes and obtain explicit confirmation before committing.

Core Features & Use Cases

  • Atomic commits: ensures each commit represents a single coherent change.
  • Interactive confirmation: prompts before running git commit to prevent accidental changes.
  • Message quality: enforces a short, punctuated title and optional body explaining the change.
  • Use Case: when preparing a feature or bugfix across multiple files, this skill ensures a clean history and traceability.

Quick Start

Draft the commit with a clear, punctuated title and confirm the proposed message when prompted.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I ensure my Git commits are atomic and reviewed before submitting?▼

Atomic Git commits are ensured by a workflow that reviews changes, stages relevant files, drafts a compliant message, and prompts for explicit confirmation before executing the commit.

Can I prevent accidental changes from being committed in my version control workflow?▼

Preventing accidental changes in version control is achieved by an interactive confirmation prompt that halts the git commit process until you explicitly review and approve the staged files.

How do I write a proper commit message for multiple file changes?▼

Writing a proper commit message for multiple file changes involves drafting a short, punctuated title summarizing the atomic change, followed by an optional body explaining the specific modifications for traceability.

What is the best way to maintain clean Git history across a multi-file feature?▼

Maintaining clean Git history across a multi-file feature is best achieved by enforcing an atomic commit process that stages relevant files together with a coherent, reviewed commit message.

Does this Git commit workflow require any external dependencies or components?▼

This Git commit workflow requires no external dependencies or additional components, operating directly within your existing version control environment to guide the staging and committing process.

Related Skills

Explore More Software Engineering Skills→
yoshihiko555yoshihiko555

commit

Stage and commit only files discussed in the conversation.

Community
Advanced
bswrundquistbswrundquist

commit-and-push

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

Community
Basic
theodrosyimertheodrosyimer

conventional-commit

Generate commitlint-compliant conventional commit messages from staged diffs.

Community
Intermediate
winsorllcwinsorllc

git-ops

Automate Git operations for commits, branches, and remote synchronization.

Community
Basic