skills.rest
liauw-media
liauw-mediaCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforce atomic Git commits with pre-commit verification and standardized messages.

3|2|Updated Oct 10, 2025
Search Tags:#code quality#git#workflow#commit messages#branching#commits
One-click install
npx skills add https://github.com/liauw-media/CodeAssist --skill git-workflow-liauw-media
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/liauw-media/CodeAssist/tree/main/skills/workflow/git-workflow
Command: npx skills add https://github.com/liauw-media/CodeAssist --skill git-workflow-liauw-media

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams maintain clean, readable Git history and consistent branching, reducing merge conflicts and making it easier to review changes.

Core Features & Use Cases

  • Small, logical commits: One logical change per commit to simplify review and debugging.
  • Verification before commit: Mandatory checks (tests, quality) run before any commit.
  • Branching & PR guidance: Clear rules for branching, merging, and PR processes to maintain a tidy history.
  • Governance for consistency: A single, auditable standard across frontend and backend work.

Quick Start

Before every commit, run the verification-before-completion workflow, write a small, focused commit describing the change, and ensure tests pass. Then proceed to merge or open a PR.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I keep my Git history clean and prevent messy commits?▼

Clean Git history requires atomic commits with one logical change each, mandatory verification before committing (tests and quality checks), and adherence to standardized commit message formats. This prevents chaotic history and makes debugging and code review significantly easier.

What's the best way to structure commits and branching for team consistency?▼

Establish a standardized workflow: use clear branching rules, write focused commit messages describing single logical changes, run pre-commit hooks for verification, and follow consistent pull request processes. This creates an auditable standard across frontend and backend work and reduces merge conflicts.

Why do I need verification checks before every commit?▼

Pre-commit verification ensures tests pass and quality checks succeed before changes enter the repository. This catches issues early, maintains code quality standards, and prevents broken commits from polluting history.

Can I use pre-commit hooks to enforce commit message standards?▼

Yes. Pre-commit hooks enforce standardized commit message formats and verify that only small, logical changes are committed. They run mandatory checks before any commit is allowed, ensuring compliance with your team's workflow rules.

How do branching and pull request guidelines prevent merge conflicts?▼

Clear branching rules and PR guidance reduce conflicts by keeping changes isolated, reviewable, and traceable. Consistent processes minimize concurrent changes to the same code and make conflict resolution straightforward.

Related Skills

Explore More Software Engineering Skills→
eavichayeavichay

git-initialize

Initialize a Git repository with an initial commit.

Community
Basic
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
relaticlerelaticle
1.5k

spatie-version-control

Apply Spatie's Git conventions to commits, branches, and pull requests.

Official
Intermediate