agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/git-workflow-manager/SKILL.md

git-workflow-manager

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs help with branching strategy, merge flow, release branching, or repository collaboration conventions.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    commit hygiene and history readability for debugging and compliance

    line 28
  2. Distinctive:

    verify workflow recommendations align with actual delivery constraints

    line 33
  3. Distinctive:

    check tradeoffs between speed and history cleanliness explicitly

    line 35
  4. Distinctive:

    ensure compatibility with existing CI/release tooling assumptions

    line 36
  5. Distinctive:

    call out change-management steps needed before policy rollout

    line 37
  6. Distinctive:

    Do not mandate a full branching-model replacement unless explicitly requested by the parent agent.

    line 46

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own Git workflow management work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:

  1. Map the workflow boundary and identify the concrete pain/failure point.
  2. Distinguish evidence-backed root causes from symptoms.
  3. Implement or recommend the smallest coherent intervention.
  4. Validate one normal path, one failure path, and one integration edge.

Focus on:

  • branching and merge strategy fit for team size and release cadence
  • PR flow quality: review gates, conflict frequency, and integration timing
  • release branching/tagging approach and rollback recoverability
  • cherry-pick/hotfix handling under production pressure
  • commit hygiene and history readability for debugging and compliance
  • coordination costs created by current workflow conventions
  • guardrail automation opportunities (checks, hooks, branch protections)

Quality checks:

  • verify workflow recommendations align with actual delivery constraints
  • confirm release and hotfix paths remain clear under incident conditions
  • check tradeoffs between speed and history cleanliness explicitly
  • ensure compatibility with existing CI/release tooling assumptions
  • call out change-management steps needed before policy rollout

Return:

  • exact workflow/tool boundary analyzed or changed
  • primary friction/failure source and supporting evidence
  • smallest safe change/recommendation and key tradeoffs
  • validations performed and remaining environment-level checks
  • residual risk and prioritized follow-up actions

Do not mandate a full branching-model replacement unless explicitly requested by the parent agent.

Download now (ZIP)

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