Git Workflow Skill
A skill and plugin for Git and GitHub: branches, Conventional Commits and a pull request path to a green merge.
- 59 ★ on the repository
- Last commit
Extended access
Why this level
- Scripts call `git` and `gh`, can merge pull requests and rebase branches, and the plugin hook blocks actions on failure.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/git-workflow-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Scripts call `git` and `gh`, can merge pull requests and rebase branches, and the plugin hook blocks actions on failure.
This is third-party code. Review the repository files before installing.
What it does
The `git-workflow` skill collects team development practices: branching with Git Flow, GitHub Flow or trunk-based, Conventional Commits messages, pull request review and merge, conflict resolution, rebasing long-lived branches and hooks via lefthook, husky or pre-commit. It ships `pr-status.sh`, `pr-merge.sh` and a conflict marker check, and the `/pr-finish` command drives a pull request to a green merged state. Critical rules are strict: no direct push to the main branch, no merge with unresolved threads, no squash unless asked and no "tested" claims without command output. The pull request tooling targets GitHub, while the reference holds `glab` equivalents for GitLab.
Who it is for. Teams on GitHub that trust an agent with branches, commits and pull requests and want consistent rules instead of improvisation.
Good fit when
- The agent writes a series of commits and they must follow Conventional Commits.
- A pull request is stuck on red CI and unresolved reviewer comments.
- A long-lived branch must catch up with the main one without losing changes in the merge.
- Pre-commit hooks are being set up and a break inside a worktree must be avoided.
Not a fit when
- The repository lives elsewhere and you need ready merge scripts: they target GitHub.
- You need to cut a release: the author has a separate skill for that.
- The agent must not be allowed to run `git` and `gh`.
Example request
Drive this pull request to merge: rebase, fix CI, answer comments and merge when everything is green.Limitations
The merge scripts use the GitHub GraphQL API and require `gh`, `git` and `uv` with Python 3.11 or newer, and `yq` for `.spec-cleanup.yml`. Installing through `npx skills` copies only `SKILL.md` files, so hooks and commands arrive only via the marketplace or the skills directory. The plugin hook fails closed from Claude Code 2.1.295. Edits inside an installed skill directory are forbidden by the skill own rules.
How to disable. Run `/plugin uninstall git-workflow@netresearch-claude-code-marketplace` or delete the `~/.claude/skills/git-workflow` directory.
FAQ
How do I install git-workflow in Claude Code?
Add the marketplace with `/plugin marketplace add netresearch/claude-code-marketplace`, then `/plugin install git-workflow@netresearch-claude-code-marketplace`. This brings the hooks and the `/pr-finish` command.
Can I install without a marketplace?
Yes: clone the repository into `~/.claude/skills/git-workflow`. Since Claude Code 2.1.157 such a folder loads by itself with its hooks and commands, but `claude plugin update` does not apply to it.
Does it work with GitLab?
Partly. Branching and commits are generic, while merge scripts and thread handling target GitHub. `glab` equivalents are described in `references/pull-request-workflow.md`.
Which rules does the skill treat as mandatory?
No direct push to the main branch, no merge with unresolved threads, no squash unless asked and no "verified" claim without pasted command output.
What does the /pr-finish command do?
It drives a pull request to merge: rebases, fixes CI, resolves reviewer comments, updates the title and description and merges when checks are green.
Discussion
No questions or reviews yet.
Related
SkillsA skill that splits changes into logical Conventional Commits and safely handles branches, pushes and pull requests.
Official Flux CD skills: Flux answers, manifest generation, GitOps repository audit and debugging of live-cluster failures
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
Four skills for GitHub Actions: CI speedup, configuration scoring, workflow attack scanning and StarSling account reports.
prek skill for agents
prek skill
The prek skill teaches an agent to set up Git hooks with prek, a Rust replacement for pre-commit: config, shims, priorities, built-in hooks and monorepos
A Git client with a built-in MCP server for Windows, macOS and Linux: an agent reads repos, PRs, issues and CI logs, read-only
README in short
The repository publishes the skill under the open Agent Skills standard and offers several install paths: marketplace, skills folder, `npx skills`, release archive, clone and Composer for PHP projects.