agentsclimarketplace

Git setup

Skill smanaton/git-coach/skills/git-setup

Hands-on git coaching skills for AI coding agents: real commands, plain-English why, undo-first recovery, and safe practice drills.

Install
npx -y skills add smanaton/git-coach --skill git-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Onboarding and environment setup for the git-coach skill set. Assesses your git experience level, checks your environment (git installed, version, Node.js for drills), and guides you to the right starting skill. Use when you're new to git-coach, want to set up git, need to check your environment, or when the current directory is empty and not a git repo. Triggers on 'teach me git', 'git setup', 'how do I get started with git', or when no git repo exists and the user seems to be a beginner. Skip when you already know which skill you need and the environment is ready.

SKILL.md

4.8 KB, as published. Nobody here has run it

git-setup

Welcome to git-coach. This skill assesses your level, checks your environment, and guides you to the right starting point.

1. Assess experience level

Ask one question:

  • "Are you new to git, have you used it a bit, or are you comfortable and want to improve?"

Map the answer:

  • Beginner (new, or only clone/push) → mental model first, then first drill
  • Intermediate (add/commit/push but get stuck) → explain the 4 skills + recommend a drill
  • Advanced (comfortable, wants to level up) → explain the 4 skills + recommend harder drills (see section 5)

2. Environment check (first run or when asked)

Run diagnostics:

git --version
node --version

Check:

  • Is git installed? What version?
  • Is Node.js installed? What version?

If git is missing:

  • macOS: brew install git or xcode-select --install
  • Ubuntu/Debian: sudo apt update && sudo apt install git
  • Windows: choco install git or winget install Git.Git
  • Always: https://git-scm.com/downloads

If git version < 2.23.0:

  • Note that some drills use git switch, which requires git >= 2.23.0
  • Suggest upgrading

If Node.js is missing:

  • Note that git-drill practice sandbox requires Node.js
  • macOS: brew install node
  • Ubuntu: sudo apt install nodejs npm
  • Windows: choco install nodejs
  • Or: https://nodejs.org/

3. Beginner path

Explain the "what is git?" mental model:

  • Git is a time machine for your code. It saves snapshots (commits) and lets you travel between them.
  • A repo is a folder git is watching.
  • HEAD is "where you are now."

Then offer:

  • "Let's practice! I can create a safe throwaway repo where you make your first commit."
  • "Say 'give me the first commit drill' and I'll start there."
  • "After that, the next step is a real merge conflict drill."

Or if they want to learn first:

  • Point to git-explain for concepts, then git-guide-me for a guided first commit.

4. Intermediate path

Explain the 4 skills briefly:

  • git-next: When you're stuck, it diagnoses your state and tells you the next move.
  • git-guide-me: When you know what you want to do, it guides you through it.
  • git-explain: When you want to understand a concept.
  • git-drill: When you want to practice in a safe sandbox.

Recommend starting with a drill based on their common pain point:

  • "I get stuck mid-rebase" → bad-reset drill
  • "I don't know what to do in conflicts" → merge-conflict drill
  • "I commit to the wrong branch" → wrong-branch drill

5. Advanced path

For someone comfortable with the basics who wants to level up:

  • Recommend the hardest drills (the ●●● ones): bad-reset and pr-conflict (request them to trigger git-drill).
  • Point to git-explain for internals worth understanding deeply — the reflog, reset modes (soft/mixed/hard), rebase vs merge.
  • Suggest git-next as a second opinion whenever they hit an unfamiliar repo state.

(Contributing to git-coach itself — running evals, adding scenarios — is documented in the repo README, not here.)

6. Empty directory / auto-detect

If the current directory is empty and not a git repo:

  • "This directory is empty. Want to run a practice drill here? I can create a safe throwaway repo for you to practice on."
  • "Or I can help you initialize a real git repo here."

If they choose drill → guide them to request one (which triggers git-drill). If they choose init → run git init and guide them to git-guide-me for their first commit.

7. Skill navigator

After setup, the user should know:

  • "I'm stuck" → git-next
  • "Show me how to do this" → git-guide-me
  • "What is this thing?" → git-explain
  • "I want to practice" → git-drill

When to use

  • "teach me git"
  • "git setup"
  • "how do I get started with git"
  • "check my git environment"
  • "I don't know which git skill to use"
  • "I want to learn git from scratch"

When NOT to use

  • Already know which skill you need → use that skill directly
  • Real problem in a git repo → git-next
  • Want to practice → git-drill
  • Conceptual question → git-explain
  • Guided operation → git-guide-me

References

  • No bundled references needed — this skill is primarily a router and environment checker.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.