skills.rest
ClankerGuru
ClankerGuruCOMMUNITY
Explore all skills by this author →
𝕏@ClankerGuruGitHub

git-workflow

Guides Git branching, commits, and PRs with enforced pre-commit and pre-push hooks.

Updated Apr 8, 2026
Search Tags:#git#workflow#branching#pre-commit#code-review#pull-request#commit-messages
One-click install
npx skills add https://github.com/ClankerGuru/opsx --skill git-workflow-clankerguru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/git-workflow
Command: npx skills add https://github.com/ClankerGuru/opsx --skill git-workflow-clankerguru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to maintain consistency and quality across Git workflows, leading to merge conflicts, brittle histories, and misaligned PRs. This Skill provides a comprehensive reference and guardrails for branch strategies, commit conventions, PR lifecycles, and pre-commit/push hooks.

Core Features & Use Cases

  • Branching policies: trunk-based development with feature/bugfix branches and mandatory PRs to main.
  • Commit conventions: imperative messages, avoiding AI-attribution, and proper body content for traceability.
  • PR lifecycle & code review: guidelines to ensure timely reviews, comments, and checks before merge.
  • Automation guards: pre-commit and pre-push hooks to enforce build and tests before integrating changes.

Quick Start

Describe a feature-branch workflow and demonstrate creating a PR that follows the policy.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is a standardized Git workflow for multi-person projects?▼

A standardized Git workflow enforces branching policies, commit conventions, and PR lifecycles to prevent merge conflicts and maintain predictable project histories across development teams.

How do I set up trunk-based development with feature branches and pull requests?▼

Create short-lived feature or bugfix branches from main, implement changes, then open a mandatory pull request for code review and automated checks before integrating back into the trunk.

Does this Git workflow support pre-commit and pre-push hooks for build automation?▼

Yes, the workflow applies pre-commit and pre-push hooks as automation guards to enforce build and test execution before integrating changes, ensuring code quality and safety.

What's the best way to write commit messages for traceability in pull requests?▼

Use imperative commit messages without AI-attribution, including proper body content to provide context for traceability and align with the enforced pull request lifecycle.

Why does my team struggle with brittle Git histories and merge conflicts?▼

Teams struggle with brittle histories when lacking consistent Git workflow governance, requiring enforced branch strategies, commit conventions, and mandatory pull request reviews to ensure alignment.

Can I use this branching strategy for small teams or does it require a specific scale?▼

This Git workflow applies to software development teams working on multi-person projects, providing explicit governance and safety guardrails suitable for any scale requiring predictable histories.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
omerakbenomerakben
1

git-workflow-deployment

Automate Git branching, CI/CD gates, and Vercel production deployments.

Community
Intermediate
mvillmowmvillmow
18

ci-run-precommit

Run pre-commit hooks to validate code before committing in local or CI workflows.

Community
Intermediate
belokonmbelokonm
8

git-workflow-manager

Design scalable Git branching models and pull request governance workflows.

Community
Advanced