# Gc

> ONLY trigger on explicit /gc. Never auto-trigger on 'commit', 'push', or similar words.

- Skill: `majiayu000/gc` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/gc`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/gc/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/gc

---


# Git Commit and Push

**Repo targeting:** If `--repo <path>` is provided, use `git -C <path>` for ALL git commands (add, commit, push). Otherwise use current directory. Strip `--repo <path>` from args before treating remainder as message.

1. `git -C <repo> add -A` (omit `-C` if no --repo)
2. If user provided a message, skip to step 4
3. `python ~/.claude/skills/gc/gc_diff.py <repo>` (omit arg if no --repo) — if it prints "No staged changes", stop and tell user. If it errors, stop and show the error. Otherwise draft from its output + conversation memory. Imperative, lowercase, no period, ~50 chars. Bullets OK for bigger changes.
4. Commit, then `git push` (or `git push -u origin <branch>` if no upstream). All with `-C <repo>` if specified.

NEVER run `git diff`, `git log`, `git show`, `git status`, or read any file to inform the message. Only inputs: script output + conversation memory. No Co-Authored-By or trailers. No selective staging.