Skills for “git”
12 skills match · 308 ms · understood as by meaning
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…
…preview stages, deploy on push (`prisma git connect`, `prisma/cloud-deploy-action`), `prisma service` logs, versions, rollback, or custom domains, `project env`, `PRISMA_SERVICE_TOKEN`, regions,…
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Operate native Git in an AIDP workspace — branches, checkout, commit/push, pull, merge, rebase, reset, diff, and conflict resolution on workspace git repositories. Use when the user wants to version workspace…
…Covers safe work in place, existing workspaces, and Git…
…human-readable release notes and CHANGELOG entries from a git commit range, grouping changes by impact and crediting contributors. Use when the user asks for release notes, a changelog, "what changed since vX", or to…
Work with Domino Projects, covering Git-based vs Domino File System (DFS) projects, creating projects (UI and API), Git credentials and repositories, file paths in runs, syncing and branches, collaborator roles and…
…force pushes to main/master, pushes and commits on main, git reset --hard and git clean -fdx, rm -rf of /, ~, .. or paths outside the project, reading .env files, SSH keys and cloud credentials, curl or wget piped to…
Resolves git merge, rebase, cherry-pick, revert and stash pop conflicts by working out what each side meant and keeping both intents, instead of picking ours or theirs. A read-only script reports the operation in…
…files), and user skills — which memsaga mirrors into a git repo (`memsaga config` shows the path, for example ~/git/memories) on every turn. Use when the user asks what a memory or CLAUDE.md said last week, when a…
Tells the story of a codebase from its git history as an entertaining documentary, with eras, key contributors, plot twists (reverts, giant commits, long silences), cursed files, and the current state, backed by a git…
…pins down the change that introduced a regression with a git bisect runner that checks both ends first, handles timeouts and flaky repros, and always restores HEAD. Then writes a failing test, fixes the root cause…