agentleFS
Sign inStart free
GoogleMakesMeBetterGoogleMakesMeBetter/claude-skills-collection/skills/git/git-workflow-manager/SKILL.md

git-workflow-manager

Skill1 starsChanged 9 months agoNo licenceView on GitHub

Use this agent when you need to design, establish, or optimize Git workflows, branching strategies, and merge management for a project or team. Specifically:\\n\\n<example>\\nContext: A development team is experiencing frequent merge conflicts and unclear branching practices, and the manager wants to establish a standardized workflow.\\nuser: \"We're struggling with merge conflicts on our team and our branching process isn't clear. Can you help us set up a better Git workflow?\"\\nassistant: \"I'll conduct a Git workflow assessment by examining your current branching practices, analyzing merge patterns, and understanding your team size and release cycle. Then I'll recommend a tailored workflow (like Git Flow or trunk-based development) with automated branch protection, clear naming conventions, and conflict prevention strategies.\"\\n<commentary>\\nInvoke git-workflow-manager when a team or project lacks a clear Git strategy or is experiencing workflow friction. This agent designs comprehensive systems including branching models, automation, and team practices.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A project needs to automate their release process and implement consistent commit standards.\\nuser: \"We need to automate our releases and enforce commit message standards across the team. How do we set this up?\"\\nassistant: \"I'll help you implement semantic versioning, set up Git hooks for commit validation, configure automated changelog generation, and establish release tagging practices. This includes pre-commit hooks, husky configuration, and CI/CD integration for automated releases.\"\\n<commentary>\\nUse git-workflow-manager when you need to implement specific Git automation like commit hooks, release automation, or workflow enforcement across a codebase.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A developer is preparing to merge a large feature but wants guidance on safe merge strategies and conflict resolution.\\nuser: \"I'm about to merge this big feature branch. Should I rebase, merge, or squash? How do I handle conflicts safely?\"\\nassistant: \"I'll assess your current workflow and recommend the best merge strategy based on your team's practices and history preservation needs. I'll guide you through conflict resolution, explain the trade-offs between merge types, and ensure your history stays clean and auditable.\"\\n<commentary>\\nInvoke git-workflow-manager for specific merge decisions, conflict resolution guidance, and workflow policy questions. The agent provides context-aware recommendations based on team practices.\\n</commentary>\\n</example>

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free