Read this in 正體中文.
A Claude Code plugin marketplace for people who aren't comfortable with git.
Its plugin, git-helper, is a beginner-friendly git assistant that acts on your behalf: you describe what you want in plain, everyday language, and it runs the right git commands for you — explaining each step and never doing anything risky without asking first. It replies in your language.
- Everyday save & upload — "save my work", "upload to GitHub" → handles
commit,push,pullfor you. - Undo & recover (the regret pill) — wrong commit message, deleted file, want to go back → prefers safe, recoverable fixes.
- Branches & merging — create/switch branches, merge, and walk through merge conflicts step by step.
- Remote & GitHub — clone, connect a remote, sync, and understand Pull Requests.
- Safety guardrails — before anything destructive (e.g.
reset --hard, discarding changes), it explains the consequence, offers a safer alternative, and asks for your confirmation first. It will never force-push on your behalf.
/plugin marketplace add milkmidi/non-tech-git-assistant
/plugin install git-helper@non-tech-git-assistant
For local development (test edits without pushing first), point the marketplace at your local copy instead:
/plugin marketplace add <local-path-to-this-repo>
/plugin install git-helper@non-tech-git-assistant
To update after changes: /plugin uninstall git-helper@non-tech-git-assistant then install again. (For the local copy, reopening a session usually picks up edits.)
-
Installed? Run
/pluginand confirmgit-helperis in the Installed list. -
Skill loaded? Skills load at the start of a conversation, so open a new session before testing triggers.
-
Behaves correctly? In a real git project folder, type these and check the responses:
You type What you should see save my workruns git status→ if onmain/master, offers a branch first → proposes a commit message for you to confirmI deleted the wrong filereassures first → recovers with a safe restore/stash, never a destructive deletehelp me force pushrefuses to run it → steers you to pullthen a normalpushIf those three behave as described, the skill is installed and triggering correctly.
Once installed, just talk to Claude in plain language. Examples:
- "help me save my work"
- "I deleted the wrong file"
- "how do I upload this to GitHub?"
- "what's a branch and how do I make one?"
The assistant replies in your own language and walks you through one step at a time.
You: save my work
Assistant: Let me check what you changed first… (runs
git status) You changed 2 files:index.html,style.css. Suggested save note: "Update homepage layout and styles" — sound good, or would you like to write your own?You: sounds good
Assistant: Done, saved ✅ (
git add -A+git commit). This is a save point on your computer — it hasn't been uploaded to GitHub yet. Want me to upload it as a backup?
You: oh no, I deleted a file
Assistant: Don't worry — this is usually recoverable 🙂 Let me check the situation… (runs
git status) The deleted file isnotes.txt, and the deletion isn't saved yet. I can bring it straight back withgit restore notes.txt— that's a safe action. Want me to do it?You: yes
Assistant: Recovered ✅
notes.txtis back to its original contents.
You: help me force push
Assistant: I won't run a force push for you
⚠️ — it overwrites what's on GitHub with your local version and can permanently erase a teammate's work, with no way to recover it. The safe way to get your changes up is usually:git pullfirst to bring in anything you're missing, then a normalgit push. Want me to do that instead? (If a force push truly is the only option, that's an advanced, risky step — best done with someone experienced.)