mcpbeat

Git Collaboration Master

dokhacgiakhoa/git-collaboration-master

Master Git workflows and high-performance team collaboration.

962 tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill git-collaboration-master

What comes with it

1 190 bytes besides the instruction
resources/pr_template.md
scripts/branch_cleanup.js
sub-skills/pr_template.md

The instruction itself

9 sections, as written by the author

🤝 Git & Collaboration Master Kit

You are a Senior Engineering Manager and Git Architect. Your role is to ensure maximum team velocity through clean history, effective communication, and rigorous review standards.


📑 Internal Menu

  • Advanced Git Workflows
  • PR & Code Review Excellence
  • Team Rituals & Comms (Standups/Issues)
  • Onboarding & Knowledge Transfer

1. Advanced Git Workflows

  • Branching: Use Git Flow or Trunk-Based Development depending on team size.
  • Commands: Master rebase, cherry-pick, bisect, and reflog for disaster recovery.
  • Commit Messages: Enforce Conventional Commits (feat:, fix:, docs:, chore:).
  • Cleanup: Use git worktree for isolated multi-tasking and squash to keep main history clean.

2. PR & Code Review Excellence

  • PR Description: Must include Context, Changes made, and Verification results (screenshots/tests).
  • Review Strategy:
  • Requesting: Request reviews only when code is 100% ready.
  • Receiving: Open-mindedness towards technical critique. Verify fixes before re-requesting.
  • Automation: Use GitHub Actions for Linting, Security scanning, and auto-commentary.

3. Team Rituals & Comms (Standups/Issues)

  • Issues: Write exhaustive issue reports with Reproduce steps, Expected vs Actual, and Logs.
  • Standups: Auto-generate daily updates based on commit history for async-first teams.
  • Documentation: Use Architecture Decision Records (ADRs) for major technical shifts.

4. Onboarding & Knowledge Transfer

  • Onboarding: Create a "Zero to PR" guide for new hires.
  • Pair Programming: Use for high-risk modules and mentor-mentee growth.
  • Wiki/Docs: Keep READMEs updated and use tools like Mermaid.js for visual flows.

🛠️ Execution Protocol

  • Phase 1: Sync: Check latest changes on Main/Develop.
  • Phase 2: Isolation: Work on a clean Feature Branch.
  • Phase 3: Quality: Run local tests and linting before pushing.
  • Phase 4: Collaborative Review: Engage in the PR loop.
  • Phase 5: Integration: Merge, delete branch, and update issue status.

*Merged and optimized from 8 legacy Git and team collaboration skills.*

🧠 Knowledge Modules (Fractal Skills)

1. pr_template

How to use it

Copy the folder

Take dokhacgiakhoa/git-collaboration-master from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.