Agent skills for Claude Code

Safely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work.

Analyzes working directory changes, generates structured commit messages, and safely commits and pushes code to remote repositories.

Git commit conventions and workflow for Bitwarden repositories.

Enforces Conventional Commits 1.0.0 standards and structured version control workflows across polyglot projects.

Use this skill immediately when the user mentions merge conflicts that need to be resolved.

Apply Singleton SD git conventions — commit format, branch naming, ticket linking, and sibling worktrees

Analyzes the previous N commits for breaking changes across the CDS public API surface.

Use when managing git workflow: creating branches, writing commit messages, preparing PRs, generating changelogs, managing releases…

Install a Claude Code PreToolUse hook that blocks dangerous git operations (force push, reset --hard, clean -f, branch -D, checkout…

Git expert for atomic commits, rebasing, and history management with style detection

You are retrieving facts from Tau Git Memory.

Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or…

Clones specified Git repositories and branches safely into designated workspace directories without overwriting existing code.

Use when planning git branching strategies or managing branches for development.

Manage git workflow for environment-based infrastructure deployments with rollback capabilities.

Use when the user asks to set up, initialize, adopt, or bootstrap a repository Git strategy, worktree workflow, or docs/git-strategy.md.

Tether (install/uninstall) hooks that enforce git-town over raw git commands in Claude Code.

Manage Git branching strategies, commit conventions, and collaboration workflows.

Make a root git repo over nested repos; skip gitlink traps.

Mechanism layer for GitCode (gitcode.com): drive the REST API and the CI gate headlessly — open/update a PR, search and open issues/RFCs…

Validate repository changes through a server-hosted Gitea Actions route and then push the identical verified commit to GitHub.