← ClaudeAtlas

gitlisted

Git and GitHub playbook with a one-look state check: branches and syncing with the remote, a rejected push, merge and rebase conflicts, searching history (who changed what and why, log -S, blame, bisect), undoing changes safely, stashes and worktrees, and GitHub through gh — issues, pull requests, review threads and comments, releases, the API. Run it yourself, without asking, for any git or GitHub work beyond a quick read, when a git command failed or a rebase/merge is in progress, and when the user mentions git, a branch, a conflict, a PR, an issue or GitHub («подтяни изменения», «разреши конфликт», «кто сменил», «что в PR», /git). Helper: scripts/git_state.py status|conflicts|review. Commits, pushes and PRs themselves: /commit and /pr.
stxrmik/antigravity-plus · ★ 1 · Code & Development · score 74
Install: claude install-skill stxrmik/antigravity-plus
# /git — Git and GitHub Run `python3 "<skill_dir>/scripts/git_state.py" status` first (`--path "<repo>"` when you aren't in it; `--fetch` to compare with the remote; `--github` for gh's login and this branch's PR). It prints the branch, ahead/behind, an operation in progress, conflicts, changes, stash, last commits, remotes, and the exact next commands. Exit 2 = not a git repository: say so; don't run git there (/git-init only when the project should have one). Who decides: reading anything, fetching, branching locally, resolving conflicts, stashing and local undo of your own work are yours to do. Commits → /commit, push and PRs → /pr (only on the user's request or under full access). Anything others see on GitHub — comments, reviews, approvals, merges, issues, releases, labels — only when the user asks for it. Destructive commands (`reset --hard`, `clean -f`, force-push, `branch -D`, `stash drop`) stop at the guard for the user: say in one line why you need them, or pick a safe way below. ## Never wait for input Nobody types into this terminal: a keyboard prompt (`-p`, gh's questions, a password) hangs forever. Antigravity sets `GIT_EDITOR=false`, so a git command that wants an editor fails at once — and `-c core.editor=…` can't change that (the variable wins); `GIT_EDITOR=true git …` does. Pagers are off (`PAGER=cat`). | Instead of | Run | |---|---| | `git commit` (opens an editor) | `git commit -m "<subject>" -m "<body>"`, or a long message: `git commit -F - <<'EOF'`