skills.rest
liveview-native
liveview-nativeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Commit Workflow Skill

Enforce atomic Git commits with descriptive messages and pre-commit checks.

1|Updated Nov 20, 2025
Search Tags:#git#workflow#best practices#version control#commit#code history
One-click install
npx skills add https://github.com/liveview-native/swiftui-modifiers-codegen --skill commit-workflow-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Workflow Skill
Source: https://github.com/liveview-native/swiftui-modifiers-codegen/tree/main/skills/commit_workflow
Command: npx skills add https://github.com/liveview-native/swiftui-modifiers-codegen --skill commit-workflow-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces disciplined Git commit practices, ensuring a clean, understandable, and manageable project history by requiring commits after each completed feature.

Core Features & Use Cases

  • Incremental Committing: Guides users to commit after every logical unit of work (feature, bugfix, refactor, docs).
  • Descriptive Commit Messages: Provides a clear format and examples for writing effective commit messages.
  • Pre-Commit Checklist: Ensures tests pass, code is formatted, and builds succeed before committing.
  • Use Case: A developer implements a new API endpoint. Instead of waiting until the end of the day, this Skill prompts them to commit the completed endpoint with a descriptive message and passing tests immediately after implementation.

Quick Start

Commit the current changes with a message describing the completed feature.

Frequently Asked Questions about Commit Workflow Skill

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

FAQPage Schema
What is an atomic Git commit and when should I use it?▼

An atomic Git commit encapsulates a single logical unit of work, such as a feature, bugfix, or refactor. You should use atomic commits immediately after completing each task to maintain a clean, understandable project history.

How do I write descriptive Git commit messages for completed features?▼

To write descriptive Git commit messages, follow a clear format that details the completed feature, bugfix, or refactor. Use provided examples to ensure your message accurately describes the specific logical unit of work.

What should I include in a pre-commit checklist for version control?▼

A pre-commit checklist for version control should verify that all tests pass, code formatting is applied, and builds succeed. Running these checks ensures your code history remains stable before committing completed features.

How does atomic committing work with TDD workflows?▼

Atomic committing integrates with TDD workflows by requiring a commit after each completed feature or bugfix. This ensures that your code history accurately reflects the test-driven development cycle and passing tests before committing.

What's the best way to structure Git history for a new API endpoint?▼

The best way to structure Git history for a new API endpoint is to commit the completed endpoint immediately with a descriptive message. This incremental approach prevents large, delayed commits and ensures passing tests are recorded.

Related Skills

Explore More Software Engineering Skills→
liuminxin45liuminxin45
95

speckit-commit

Create validated multi-repository commits with CoreRuntime commit-message compliance.

Community
Advanced
jikimejikime
5

jikime-workflow-changelog

Generate categorized changelogs from Git commits with breaking change detection.

Community
Advanced
BedriftsgrafenBedriftsgrafen

Git Commit Convention

Enforce the Bedriftsgrafen project's git commit message format and pre-commit checks.

Official
Advanced
maggitmaggit

rebase

Plan and execute non-interactive git rebase operations with safety checks.

Community
Intermediate