Git Plain Speak Assistant

Problem

Git failures are usually not syntax errors, but missing context: current branch, uncommitted changes, remote ahead/behind status, and whether an operation is reversible. A request like “back it up”, “pull it”, or “undo that commit” can become risky if translated directly into git push, git pull, or git reset --hard without checking the repository first. Git Plain Speak maps plain-language intent to a bounded, confirmable Git workflow.

How It Works

The skill operates on the current working directory repository and first runs scripts/git_status_summary.py to collect a structured state snapshot: repository flag, current branch, changed files, ahead/behind status, recent commits, and remote. It then routes the request:
- GitHub setup: checks gh CLI and auth, guides browser device-code login, and creates or connects a repository before pushing.
- Backup: reviews git diff --stat, proposes a concise Chinese commit message, and runs git add, git commit, and git push only when appropriate.
- Query: explains changes and history with git status, git log, git blame, and git show.
- Rollback: distinguishes uncommitted, unpushed, and pushed changes, preferring git restore, git reset, and git revert, with explicit confirmation for destructive cases.
- Branches: creates, switches, merges, and deletes branches, and during conflicts lists the conflict points instead of silently editing logic.

Boundaries

It is best for solo projects, GitHub public or private repositories, and everyday commit/branch work where “inspect first, act second” matters. If no remote exists, it guides setup instead of pushing blindly. Non-fast-forward rejections, merge conflicts, and irreversible operations trigger impact summaries and explicit user confirmation. It does not replace code review, CI security controls, team Git policy, or complex sandbox, network, and permission fixes.