agency-git-workflow-master

Enforce atomic commits and conventional commit messaging across development teams.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-git-workflow-master-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-git-workflow-master
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-git-workflow-master
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-git-workflow-master-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the common friction of messy commit histories, complex merge conflicts, and inefficient branching strategies that often plague collaborative software development.

Core Features & Use Cases

  • Workflow Optimization: Provides expert guidance on choosing between Trunk-Based development and Git Flow based on team size and release needs.
  • History Maintenance: Offers precise instructions for interactive rebasing, squashing commits, and maintaining atomic, conventional commit messages.
  • Advanced Recovery: Assists in utilizing Git worktrees, bisecting for bug hunting, and safely resolving merge conflicts without losing work.

Quick Start

Ask the git workflow master to guide you through an interactive rebase to clean up your current feature branch before submitting a pull request.

Frequently Asked Questions about agency-git-workflow-master

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

FAQPage Schema
How do I clean up a messy commit history before submitting a pull request?

To clean up a messy commit history, use interactive rebasing to squash commits and rewrite messages. This enforces atomic commits and conventional messaging, ensuring your feature branch remains structured before submission.

What is the best way to choose between Git Flow and Trunk-Based development?

Choosing between Git Flow and Trunk-Based development depends on your team size and release needs. Evaluating these factors helps standardize version control practices and optimize repository branching methodologies.

How do I safely force push after rewriting commits during an interactive rebase?

To safely force push after rewriting commits during an interactive rebase, use safe force-pushing techniques. This ensures repository integrity is maintained without overwriting remote changes from other collaborators.

Can I use Git worktrees to manage multiple branches simultaneously?

Yes, you can use Git worktrees to manage multiple branches simultaneously. Worktree management allows you to check out multiple branches in separate directories, facilitating advanced recovery and bug hunting without switching contexts.

How does bisecting help with bug hunting in complex branching methodologies?

Bisecting helps with bug hunting by systematically narrowing down the commit that introduced a regression. Combined with structured branching methodologies, it isolates defects efficiently while maintaining overall repository integrity.