← ClaudeAtlas

gaclisted

Git add and commit helper, with shorthands that go further. Use this skill whenever the user types "/gac" or "gac", or asks to stage and commit files. The shorthands "gacp" (commit + push), "gacpp" (commit + push + open a PR), "gacppm" (commit + push + PR + merge) and "gacppmr" (all that + a release) have their own skills that follow this one. Sources nvm first when it is installed (NVM_DIR is unset in the Bash tool shell) so Husky pre-commit hooks work correctly. Opens and merges PRs on GitHub (gh), Bitbucket Cloud and self-hosted Forgejo/Gitea (bundled scripts, REST APIs); a merge always waits for the user to confirm it. Accepts optional arguments: files to stage and a commit message. If not provided, checks git status and prompts interactively. Never includes the JIRA ticket in the commit message — Husky prepends it automatically from the branch name.
webdevnerdstuff/claude-marketplace · ★ 1 · Code & Development · score 77
Install: claude install-skill webdevnerdstuff/claude-marketplace
# Git Add & Commit (gac) ## What this skill does Stages files and creates a git commit, making sure nvm is sourced first when it is installed, so Husky hooks (lint-staged, commit-msg hooks, etc.) can run without failing. ## Why nvm is sourced first The Bash tool starts with `NVM_DIR` unset. Without it, nvm can't find its installation and tries to write to root paths (`/alias`, `/.cache`) which are read-only in this environment, causing Husky hooks to crash before they even run. Sourcing nvm at the start of the command fixes this. When nvm isn't installed (no `~/.nvm/nvm.sh`), the step is skipped and git runs as normal. ## Authorization Invoking `/gac` is explicit, one-time authorization to stage and commit the determined files — do not ask "should I commit?" or "ready to proceed?" before step 3. Only pause for confirmation if the files/message are genuinely ambiguous (per step 1/2 below). This authorization is scoped to this skill only. Outside of `/gac`, never stage or commit files on your own initiative without asking first. ## Shorthands Each letter after `gac` adds a step, run in this order, stopping at the first failure and reporting it: | Typed | Steps | | --- | --- | | `gac` | commit | | `gacp` | commit, push (`git push -u origin <branch>`) | | `gacpp` | commit, push, open a PR into the repo's default branch | | `gacppm` | commit, push, open a PR, **ask the user once to confirm the merge** (see **Merging** below), wait for CI to pass, merge it (a merge commit