250 free skills · page 5 of 5
Git Workflows skills
Skills for git — commit message conventions, branching strategy, rebase workflows, merge conflict resolution, and git hooks.
Real files from public repositories — hand-curated, never invented. Sorted by installs.
5 / 5page
gitkraken-cliits-a-unixsystem/skillsUse the GitKraken CLI (gk) for git operations instead of raw git/gh commands. Activate this skill whenever performing git operations like committing, creating PRs, pushing, resolving conflicts, explaining changes, generating changelogs, or managing branches and work items. Even if the user doesn't mention "gk" or "GitKraken" explicitly, use gk commands for any git workflow where gk has a matching command, falling back to raw git only for operations gk doesn't cover.Git Workflows4
git-commitshipurjan/skillsExecute 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 groupingGit Workflows4
cz-git-stylezccz14/skillsEnforce CZ's Git and GitHub delivery style with gitmoji commits, protected main, repository-local worktrees, squash-only Auto Merge, pull-request monitoring, GitHub Actions verification, and safe cleanup. Use whenever Codex sets up or updates a GitHub repository, creates a feature worktree, prepares or opens a pull request, follows a pull request through merge and Actions, or performs the associated Git workflow.Git Workflows4
monorepo-worktree-safetyzenstudiolab/skillsPrevents 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 Workflows4
splitiron-ham/splitSplit a large branch into N stacked logical branches with hunk-level granularityGit Workflows3
git-worktree-feature-flowalessandrobologna/codex-skillsCreate a feature branch in a Git worktree, work independently, then merge back and clean up safely.Git Workflows3
git-commit-hygienejohnefemer/skillfishInstall git hooks that auto-strip AI tool attribution from commits — blocks Co-Authored-By lines AND AI author hijacking.Git Workflows3
git-rebase-helparyan1718/developer-agent-skillsUse this skill when the user invokes git-rebase-help, mentions rebasing a branch, asks how to bring a branch up to date, or needs mid-rebase conflict help. Triggers on: "git-rebase-help", "rebase this branch", "bring this branch up to date", "mid-rebase conflict help", or similar Git rebase workflow requests. Guide the workflow step-by-step through repository checks, target branch selection, working tree preparation, conflict resolution, and post-rebase cleanup, with confirmation required before any history-rewriting, content-changing, or destructive Git action.Git Workflows3
git-commithebilicious/skillsExecute 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 groupingGit Workflows3
git-czimrea/skillsExecute 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 from changes, (2) Generating cz-git/czg-style conventional commit messages from diff, (3) Extracting ticket ID from branch name, (4) Intelligent file staging for logical groupingGit Workflows3Other tasks
same rules, different job
