BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

git-workflow-skill

Skill Productivity Poor
Works inClaude Code
Poor Scanned — metadata only

Enforces consistent branching and commit patterns across teams, reducing merge conflicts and review friction.

Agent Skill for Git workflow best practices - branching, commits, PR workflows | Claude Code compatible

36 starsFreeQuick setup
Below standard — Significant caveats apply. Not recommended without careful review of the security and evaluation sections.

Enforces consistent branching and commit patterns across teams, reducing merge conflicts and review friction. Cuts onboarding time for developers unfamiliar with your repo's workflow.

Engineering teams building on Claude Code who need automated git workflow guidance without manual policy enforcement.

Claude Code Claude Cowork Claude Chat

https://github.com/netresearch/git-workflow-skill

By netresearch

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
claude plugins install netresearch/git-workflow-skill

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me auto-suggest branch names based on ticket or feature type
CostFree

Trust Signals Auto-scanned

Stars36Contributors4Last updated2026-07-24Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-25 · scanner v1

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 4 contributors; last commit 1d ago; license no license.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
1/5
Versatility
2/5
Reliability
4/5
Security
3/5
Overall score2.30 / 5.00 PoorEvaluatedJul 2026
Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 4 contributors; last commit 1d ago; license no license.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →