mcpField
G
git-workflow

git-workflow

github.com/netresearchDevelopment59730 installsUpdated today
Repository

About git-workflow

git-workflow is a skill for developers that provides Git procedures for branching, commits, hooks, and pull requests, with GitHub-specific merge checks. It emphasizes explicit safety rules, verification evidence, and reference workflows for advanced operations.

Key features

  1. 01Rules for branching and commits
  2. 02Conventional commit guidance
  3. 03Git hook detection and setup references
  4. 04GitHub PR status and merge scripts
  5. 05Merge gates for review, CI, and threads

Use cases

  1. 01Prepare commits and branches consistently
  2. 02Check PR readiness before merging
  3. 03Diagnose hook or advanced Git workflows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/netresearch/git-workflow-skill --skill git-workflow

After installing, type/git-workflowin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

checkpoints.yaml
evals/
evals.json
references/
advanced-git.md
ci-cd-integration.md
claude-code-hooks.md
code-quality-tools.md
commit-conventions.md
git-hooks-setup.md
github-releases.md
merge-gate-watcher.md
no-editorializing.md
pull-request-workflow.md
spec-cleanup.md
scripts/
conflict-marker-gate.py
merge-gate.sh
pr-merge.sh
pr-status-evaluate.jq
pr-status-investigate.jq
pr-status.sh
pr-sweep.sh
repo-contribution-preflight.sh
signing-preflight.sh
spec-cleanup-guard.sh
verify-git-workflow.sh

Details

From the project README

Git Workflow Skill

Not Here

Releases: github-release. BLOCKED-PR diagnosis: github-project.

GitHub only. Everything below the branching and commit sections — pr-status.sh, pr-merge.sh, the merge gate, review threads — speaks GitHub GraphQL. For a GitLab merge request the equivalent glab calls are in references/pull-request-workflow.md § GitLab: the same gate with glab.

Critical Rules (Non-Negotiable)

  1. No direct push to main — always open a PR.
  2. No merge before all threads resolved (references/pull-request-workflow.md).
  3. No squash unless asked — preserves atomic commits, signatures, bisection.
  4. No "tested/verified/working" without pasted command output — else say so.
  5. No edits to installed skill/plugin cache paths (~/.claude/skills/, ~/.claude/plugins/cache/, **/.bare/**) — always the repo worktree, verified by pwd.
  6. Force-push only with --force-with-lease — never plain --force.
  7. Commit before rebase — add → commit → fetch → rebase → push (a dirty tree aborts it).
  8. No editorializing — state what changed, not how good it is (references/no-editorializing.md).

Reference Files

ReferenceContent Triggers
references/commit-conventions.mdConventional commits, DCO sign-off
references/pull-request-workflow.mdPR merge gate, signed rebase, posting a review with inline suggestions
references/ci-cd-integration.mdCI watching, git mirrors
references/advanced-git.mdRebase (incl. non-interactive rebase -i), cherry-pick, bisect, stash, worktrees, reflog, hanging push/fetch (SSH mux), parsing git output in a script (flags that pin diff/log/status output against user config), fetching one branch in a single-branch clone (refspec)
references/github-releases.md→ github-release skill
references/git-hooks-setup.mdHook frameworks, hooks per stage
references/claude-code-hooks.mdsettings.json merge gate, cache-path rejection, auto-lint
references/code-quality-tools.mdshellcheck, shfmt, git-absorb, difftastic
references/merge-gate-watcher.mdWaiting on a gate, a watcher the harness killed, merge-driver loop, check taxonomy, stale-SHA rerun
references/spec-cleanup.mdPlanning artifacts off the base branch
references/no-editorializing.mdNo self-praise, no narrating the expected

Conventional Commits

<type>[scope]: <description>

feat MINOR, fix PATCH; full type list and DCO sign-off in references/commit-conventions.md. Breaking: ! after type, or BREAKING CHANGE: in the footer. Branches: feature/TICKET-123-description, release/1.2.0

Hook Detection

ls lefthook.yml .lefthook.yml captainhook.json .pre-commit-config.yaml .husky/pre-commit 2>/dev/null || echo "No hooks"

Install commands per framework: references/git-hooks-setup.md.

PR Merge Requirements

Before merging: threads resolved, CI green (incl. annotations), rebased, signed, and reviewed on the current head — by a human, a bot, or the author through pr-merge.sh --self-reviewed. A review is mandatory; a bot review is not, and one is waited for only while it is actually in flight. Rebase-only + signed: git merge --ff-only.

Verification

./scripts/verify-git-workflow.sh /path/to/repository
# Gate state, next action:
./scripts/pr-status.sh [-R owner/repo] [PR] [--json] [--watch]
# Merge; refuses when the gate is shut:
./scripts/pr-merge.sh [-R owner/repo] [PR] [--dry-run|--self-reviewed]
# Many PRs (`owner/repo N` per line) to merge; stops on any NEXT it does not handle:
./scripts/pr-sweep.sh [--interval SEC] [--timeout SEC] [--attention FILE] LISTFILE
# What a repository expects, before the first artifact:
./scripts/repo-contribution-preflight.sh [--repo <dir>] [--section docs|templates|packaging|ci|tools]
# Which copy is installed here (every script answers this):
./scripts/pr-status.sh --version

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

Comments

Markdown supported