376 free skills
Git Workflows skills
Skills for git — commit message conventions, branching strategy, rebase workflows, merge conflict resolution, and git hooks.
Sourced from real, public repositories — synced daily, never invented.
376 free skills
Skills for git — commit message conventions, branching strategy, rebase workflows, merge conflict resolution, and git hooks.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
install-hooks
gitguardian/agent-skills
Install ggshield as a hook so secrets are caught before they leak. Covers git hooks (pre-commit and pre-push) that block secrets from entering git history, and AI-assistant hooks (claude-code, codex, copilot, cursor, vscode) that scan an AI coding tool's prompts, actions, and outputs in real time. Use when asked to install Claude Code, Cursor, Copilot, or git hooks, or to block secrets from being committed or pushed.
git-flow-master
upex-galaxy/agentic-qa-boilerplate
End-to-end Git operator for any branching strategy. Auto-detects the project's strategy (solo-main, main+integration, enterprise multi-branch, trunk-based, GitFlow, GitHub Flow, GitLab Flow, SDET integration-trunk for chained test-automation suites) from .git config, branches, and the `git_strategy:` block in `.agents/project.yaml`, then adapts every commit, branch, push, PR, conflict-fix, and chained-PR action to that strategy. Use this skill whenever the user wants to: create a branch (`crear branch`, `new feature branch`, `start work on UPEX-123`), commit changes (`commit this`, `commitear esto`, `make a commit`, `commit and push`), push code (`push`, `push to main`, `push to staging`, `subir cambios`), open a pull request (`create PR`, `open PR`, `abrir PR`, `crear pull request`, `gh pr create`), fix merge conflicts (`fix conflict`, `resolver conflicto`, `merge conflict`, `rebase conflict`, `push rejected`), plan stacked or chained PRs (`stack of PRs`, `chained PRs`, `split this PR`, `PR demasiado grande`), set up an isolated git worktree (`worktree`, `work in a worktree`, `isolate this work`, `parallel session`, `aislar el trabajo`, `trabajar aislado`), set up or bootstrap a branching strategy on a fresh repo (`set up our git strategy`, `bootstrap branching`, `configura el flujo de git`, `git strategy setup`, `materialize the git flow`, `create the staging branch and write the runbook`), or pick / change / set up a branching strategy (`git flow`, `git strategy`, `branching strategy`, `which git flow do we use`, `set up our git strategy`, `bootstrap branching`, `configura el flujo de git`). Trigger even when the user does not say `git-flow-master` literally — if the work is git-or-PR-shaped, this is the right tool. Do NOT use for: testing tickets (use /sprint-testing), authoring test cases in TMS (use /test-documentation), writing automated tests (use /test-automation), running regression suites (use /regression-testing), or general code editing — git-flow-master operates strictly on the version-control layer.
git
alicoder001/agent-skills
Conventional Commits standard for consistent commit messages. Use when committing code, reviewing commit history, or setting up git workflows. Includes commit types, scopes, and breaking change format.
git-squash-rebase
theoklitosbam7/skills
>
git-commit
insulinocytus/skills
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
verasic-git-commits-audit
milkywayrules/verasic-skills
Pre-push commit history audit against the Verasic commit convention. Use when the user asks to "audit commits", "check commit messages", "clean commit history", or before push/PR to verify branch history.
ss-branch-strategy
jsirish/workflow-skills
Establish consistent branch-naming and default-branch conventions across all module repos when executing a major framework or CMS version upgrade. Covers integer branch naming, default-branch promotion, previous-version preservation, and the fork-and-upstream workflow for third-party modules. Use when planning or executing a major version upgrade across a suite of repos.
git-convention
duckyman-ai/agent-skills
Write conventional git commit messages following the Angular commit convention format. Use this skill whenever writing commit messages, creating commits, reviewing git history, generating changelogs, or any task involving git version control. Triggers when you see "commit", "git commit", "commit message", "changelog", "version control", "git history", "semantic commit", "conventional commit", or when the user asks to commit changes, create a PR, or review commit history. Also use when setting up commit linting or husky hooks for enforcing commit conventions.
rebase
verygoodopensource/vgv-wingspan
Rebases the current feature branch onto the base branch (main/master/develop).
cms-branches-aliases
contentstack/contentstack-agent-skills
Advise developers on using Contentstack branches for isolated content development and aliases for zero-downtime content deployments. Cover branch strategy, branch-specific vs global modules, CI/CD integration, merge behavior, and rollback patterns.
git-commit
hebertpaziam/skills
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
commit
myuon/ccskills
Conventional Commitsに従ってgit commitを実行
hr-conflict-resolution
tuanductran/hr-skills
Help HR managers with workplace conflict resolution. Use when asked to resolve a workplace conflict, mediate between employees, facilitate a difficult conversation, develop conflict resolution training, address a team dispute, create a conflict resolution policy, or any workplace conflict task.
git-workflow
pfangueiro/claude-code-agents
Git workflow conventions and conflict/recovery procedures — Conventional Commits format, branching models (Git Flow, GitHub Flow, trunk-based), pull request structure and review checklists, merge-versus-rebase choice, cherry-pick, interactive rebase, and guarded use of history-rewriting or destructive commands. Covers the rebase inversion where --ours is the upstream and --theirs is the user's own work. Use when resolving a merge or rebase conflict, choosing or documenting a branching strategy, writing a commit message or PR description to a convention, deciding between merging and rebasing, undoing or reverting a commit, cleaning up history before a PR, or recovering work after a bad reset, rebase, or force-push. Not needed for routine single commands whose syntax is already known — git status, git add, git diff, git log, staging, a plain commit, or a straightforward push or pull.
commit
myuon/agent-skills
Conventional Commitsに従ってgit commitを実行
conflict-resolution
troykelly/codex-skills
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
gh-subtrees
nikhilmaddirala/gtd-cc
Subtree publishing and project graduation. Publish monorepo changes to standalone GitHub repos, graduate projects from lab to production.
gh-subrepo
nikhilmaddirala/gtd-cc
Stateful bidirectional sync for subtree directories using git-subrepo. Sync monorepo subdirs with standalone GitHub repos and graduate projects from lab to production.
committing-changes
bitwarden/ai-plugins
Git commit conventions and workflow for Bitwarden repositories. Use when committing code, writing commit messages, or preparing changes for commit. Triggered by "commit", "git commit", "commit message", "prepare commit", "stage changes".
commit-changes
tldraw/tldraw
Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.
bf-archive-sprint
khaki4/my_skills
스프린트 내 모든 에픽이 완료된 후 스프린트 문서를 아카이빙한다. 문서 이동, git commit을 자동으로 수행한다.
branch-discipline
troykelly/codex-skills
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
install-precommit
zbruhnke/claude-code-starter
Install the pre-commit review hook that forces you to understand changes before committing. Use when you want to enable commit reviews or when setting up a new project.
committing-android-changes
bitwarden/android
Git commit conventions and workflow for Bitwarden Android. Use when committing code, writing commit messages, or preparing changes for commit. Triggered by "commit", "git commit", "commit message", "prepare commit", "stage changes".
clean-copy
tldraw/tldraw
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits.
fs-daily-report
full-scale-teams/fs-daily-report
Drafts a non-technical daily work report from your latest Git commits (GitHub CLI, GitHub MCP, or GitLab MCP) and your active Jira tickets (Atlassian Rovo MCP). Use when the user asks for a daily report, standup update, EOD summary, client update, progress report, or 'what did I do today'. Runs a prerequisite check first, lets the user pick the reference Jira ticket from a picker widget, then emits a fixed-format stakeholder-ready summary with the technical detail translated into business language.
port-conflict-resolution
pmarashian/cursor-agent-skills
Check port availability before starting server, provide patterns for killing processes on ports, document automatic port selection strategies, include fallback port ranges, and provide health check patterns. Use when dev server fails to start due to port conflicts.
resolving-merge-conflicts
carlitose/agent-skills
Trace both sides of an in-progress Git merge or rebase conflict, resolve compatible intent with scoped authority, and gate incompatible intent. Use only when the user explicitly asks to inspect or resolve current conflicts.
git-hooks
1mangesh1/dev-skills-collection
Git hooks setup with Husky, lint-staged, lefthook, and native hooks for automated code quality. Use when user asks to "setup pre-commit hooks", "add husky", "lint on commit", "format before commit", "run tests on push", "setup git hooks", "validate commit messages", "enforce conventional commits", "detect secrets in commits", "configure lefthook", "share git hooks", "core.hooksPath", "hook bypass", "debug git hooks", or automate code quality checks.
git-commit
tungxuan1656/harness-slim
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-cm
toilahuongg/shopify-agents-kit
Commit changes to git with a descriptive conventional commit message. Use when ready to commit staged or unstaged changes.
conflict-resolve
manastalukdar/ai-devstudio
Guided conflict resolution with semantic analysis and validation
git-guardrails-claude-code
costicapuntaru/agentica
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
git-merge-conflict-resolution
kentoshimizu/sw-agent-skills
Resolve Git merge/rebase conflicts with explicit intent tracking and post-resolution verification. Use when conflicts occur and intent-preserving resolution is required before integration; do not use for CI workflow design or application behavior implementation.
rebase
mishamsk/skills
Rebase the current branch onto the latest trunk ref, resolve conflicts deliberately, and run repository verification.
git-branch-strategy
kentoshimizu/sw-agent-skills
Define branch topology, lifecycle rules, and merge policy that match team delivery and release risk. Use when branch protection, release/hotfix flow, and merge discipline must be explicit to prevent unsafe history changes; do not use for CI workflow design or application behavior implementation.
branch
nicotinez/skills
>
branches
nyelonong/galdr
Use when starting work on a new branch or worktree, or when a branch's implementation is done and it needs gates, review, a smoke sheet, and a decision about merge/push. Invoke via route or explicit command.
git-workflow
clay-hhk/claude-skills
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.
commit
manastalukdar/ai-devstudio
Analyze changes and create meaningful conventional commits with pre-commit quality checks
git-rebase-workflow
kentoshimizu/sw-agent-skills
Linearize local branch history with safe rebase practices before integration. Use when branch history cleanup is needed and rebase risks (conflicts, dropped commits, rewritten history impact) must be controlled; do not use for CI workflow design or application behavior implementation.
x-git
x-cmd/skill
This skill provides comprehensive Git and code hosting platform management tools through x-cmd CLI, including GitHub, GitLab, Codeberg, Forgejo integration, and Git hooks management. This skill should be used when users need to manage Git repositories, work with code hosting platforms, automate Git workflows, or configure Git hooks from command line interfaces.
commit-message
diegoos/skills
>-
fix-merge-conflicts
aniondev/aniondevpublicskills
Resolves complicated merge conflicts in a git repository (merge, rebase, cherry-pick or stash-pop conflicts), by reconstructing the intent of both sides from the history instead of guessing from the conflict markers. Use when the user asks to resolve/fix merge conflicts, when a merge, rebase or cherry-pick stopped with conflicts, or when a conflict is too large or too semantic to resolve by simply picking one side.
git-workflow-guide
asiaostrich/universal-dev-standards
|
branch-finish
manastalukdar/ai-devstudio
Complete branch workflow with squash, rebase, and cleanup
branch-creator
adonis0123/adonis-skills
Create safe Git feature or hotfix branches with concise names. Use this whenever the user asks to create a branch, start work on a new feature or fix, wants a `feat/...` or `hotfix/...` branch name, asks for a short branch slug from a task description, or wants help before beginning local Git work. Default to recommending the branch name and command first, then create only after user confirmation. Do not push, commit, rebase, or create PRs.
merge-strategy
manastalukdar/ai-devstudio
Intelligent merge/rebase strategy selection with safe execution
git-commit
shipurjan/skills
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-commit
liao666brant/agent-tools
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/git-commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
merge-conflict-resolver
auldsyababua/instructor-workflow
Analyze branch divergence, detect potential conflicts, and guide merge resolution for any Git repository. Auto-detects current branch or accepts parameters.
resolving-merge-conflicts
bhagyamudgal/skills
Resolve an in-progress git conflict without a silent drop. Use when the worktree is mid-merge, mid-rebase, mid-cherry-pick or mid-stash-pop — `CONFLICT (content)`, `<<<<<<<` markers, `Unmerged paths`, or `fix conflicts and then commit the result`.
branch
dnd-mapp/agent-skills
Create a git branch named for the work about to happen, deriving the type and slug from the diff, a known issue, or a description. Use when the user wants to start new work or asks to create a branch, or when another skill needs a branch before it can proceed.
sync-with-primary
berrydev-ai/skills
>-
monorepo-worktree-safety
zenstudiolab/skills
Prevents dependency resolution failures and test discovery disasters when using git worktrees inside monorepos or submodules. Use this skill whenever: (1) creating a git worktree anywhere inside a monorepo or submodule directory, (2) you see errors like 'vitest: not found', unresolved @org/* or workspace:* packages from a worktree path, (3) test suites are running unexpectedly duplicate or foreign tests, (4) someone asks to run coverage or CI checks from a branch worktree, (5) setting up parallel feature development in a monorepo using worktrees. If the user mentions worktrees AND a monorepo, always apply this skill — don't assume the environment is already safe.
git-commit
yuler/skills
Use when the user wants to commit staged changes, asks for a commit message, or wants a concise summary of the staged diff before committing.
monorepo-architecture
thejoaov/skills
Use when setting up, organizing, or reasoning about a TypeScript monorepo. Covers workspace managers (Bun, pnpm), Turborepo pipelines and caching, package boundary conventions (apps/packages/tooling tiers), dependency management with catalogs and version pinning, shared tooling packages, and cross-workspace build orchestration. Trigger when the user asks about monorepo structure, where to add a new package, how to configure Turborepo tasks, or how to manage shared dependencies.
git-workflow-guide
asiaostrich/universal-dev-skills
|
hooks
andrewkamphey/video-ideas
>-
git-guardrails-claude-code
fullheart/mattpocock-skills-opencode
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.