How do I install the Git Workflow skill?

Run npx skillmds@latest add ninjasln-labs/git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Workflow?

NinjaSln-labs (@ninjasln-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Workflow by ninjasln-labs — Agent Skill

Name: Git Workflow
Author: NinjaSln-labs

Git Workflow

Git workflow skill: branching strategies, Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (CI verification, auto-merge queues, post-merge cleanup), PR review threads, signed commits, merge conflicts, Git+CI/CD integration, git hooks (lefthook, captainhook, husky, pre-commit), and debugging hook-install failures in git worktrees. Use when doing any of the above. NOT for: creating releases (use github-release) or diagnosing BLOCKED/won't-merge PRs (use github-project).

NinjaSln-labs 0e8375b 16 files · 218.7 KB Updated Sep 17, 2026

File contents

Git Workflow Skill

Critical Rules (Non-Negotiable)

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

See references/pull-request-workflow.md for merge-gate and atomic-commit patterns.

Reference Files

Load on demand:

Reference	Content Triggers
`references/commit-conventions.md`	Conventional commits, DCO sign-off
`references/pull-request-workflow.md`	Default-branch check, PR merge, merge gate, signed rebase
`references/ci-cd-integration.md`	Watching CI from the CLI, git mirror repositories
`references/advanced-git.md`	Rebase, cherry-pick, bisect, stash, worktrees, reflog, recovery
`references/github-releases.md`	Pointer to the `github-release` skill
`references/git-hooks-setup.md`	Hook frameworks, detection, hooks per stage
`references/claude-code-hooks.md`	Claude Code `settings.json` hooks — merge gate, cache-path rejection, auto-lint
`references/code-quality-tools.md`	shellcheck, shfmt, git-absorb, difftastic
`references/merge-gate-watcher.md`	Merge-driver loop, check taxonomy, stale-SHA rerun, review-bot rounds
`references/spec-cleanup.md`	Keep planning artifacts off the base branch; guard + capture-to-ADR
`references/no-editorializing.md`	Writing without self-praise or narrating the expected

Conventional Commits

<type>[scope]: <description>

Types: feat (MINOR), fix (PATCH), docs, style, refactor, perf, test, build, ci, chore, revert

Breaking change: Add ! after type or BREAKING CHANGE: in footer.

Branch Naming

feature/TICKET-123-description
fix/TICKET-456-bug-name
release/1.2.0
hotfix/1.2.1-security-patch

Hook Detection

Detect hooks first:

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

Install: lefthook install | composer install | npm install | pre-commit install

Critical Release Rules

Immutable releases: deleted releases block tag reuse; bump version.
Multi-branch releases: Use --latest=false from non-default branches.
Pre-release: Version bumped, CI green, CHANGELOG updated, git pull BEFORE gh release create.

PR Merge Requirements

Before merging: threads resolved, CI green (incl. annotations), rebased, signed. Rebase-only + signed: git merge --ff-only.

Verification

./scripts/verify-git-workflow.sh /path/to/repository

Contributing: https://github.com/netdelegated-research/git-workflow-skill

---name: git-workflowdescription: Git workflow skill: branching strategies, Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (CI verification, auto-merge queues, post-merge cleanup), PR review threads, signed commits, merge conflicts, Git+CI/CD integration, git hooks (lefthook, captainhook, husky, pre-commit), and debugging hook-install failures in git worktrees. Use when doing any of the above. NOT for: creating releases (use github-release) or diagnosing BLOCKED/won't-merge PRs (use github-project).---# Git Workflow Skill## Critical Rules (Non-Negotiable)1. **No direct push to main** — always open a PR.2. **No merge before all threads resolved** — see `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`. Dirty tree aborts rebase.8. **No editorializing** — state what changed, not how good it is; no narrating expected results or self-praise. See `references/no-editorializing.md`.See `references/pull-request-workflow.md` for merge-gate and atomic-commit patterns.## Reference FilesLoad on demand:| Reference | Content Triggers ||-----------|-----------------|| `references/commit-conventions.md` | Conventional commits, DCO sign-off || `references/pull-request-workflow.md` | Default-branch check, PR merge, merge gate, signed rebase || `references/ci-cd-integration.md` | Watching CI from the CLI, git mirror repositories || `references/advanced-git.md` | Rebase, cherry-pick, bisect, stash, worktrees, reflog, recovery || `references/github-releases.md` | Pointer to the `github-release` skill || `references/git-hooks-setup.md` | Hook frameworks, detection, hooks per stage || `references/claude-code-hooks.md` | Claude Code `settings.json` hooks — merge gate, cache-path rejection, auto-lint || `references/code-quality-tools.md` | shellcheck, shfmt, git-absorb, difftastic || `references/merge-gate-watcher.md` | Merge-driver loop, check taxonomy, stale-SHA rerun, review-bot rounds || `references/spec-cleanup.md` | Keep planning artifacts off the base branch; guard + capture-to-ADR || `references/no-editorializing.md` | Writing without self-praise or narrating the expected |## Conventional Commits```<type>[scope]: <description>```**Types**: `feat` (MINOR), `fix` (PATCH), `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`**Breaking change**: Add `!` after type or `BREAKING CHANGE:` in footer.## Branch Naming```feature/TICKET-123-descriptionfix/TICKET-456-bug-namerelease/1.2.0hotfix/1.2.1-security-patch```## Hook DetectionDetect hooks first:```bashls lefthook.yml .lefthook.yml captainhook.json .pre-commit-config.yaml .husky/pre-commit 2>/dev/null || echo "No hooks"```Install: `lefthook install` | `composer install` | `npm install` | `pre-commit install`## Critical Release Rules1. **Immutable releases**: deleted releases block tag reuse; bump version.2. **Multi-branch releases**: Use `--latest=false` from non-default branches.3. **Pre-release**: Version bumped, CI green, CHANGELOG updated, `git pull` BEFORE `gh release create`.## PR Merge RequirementsBefore merging: threads resolved, CI green (incl. annotations), rebased, signed. Rebase-only + signed: `git merge --ff-only`.## Verification```bash./scripts/verify-git-workflow.sh /path/to/repository```---> **Contributing:** <https://github.com/netdelegated-research/git-workflow-skill>

Frequently asked questions