How do I install the Git Wizard skill?

Run npx skillmds@latest add garphengate/git-wizard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Wizard safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Wizard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Wizard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Wizard?

GarphenGate (@garphengate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Wizard by garphengate — Agent Skill

Name: Git Wizard
Author: GarphenGate

File contents

Gitignore Builder

Free gateway skill from the Git Wizard bundle by GarphenGate.

Build the .gitignore your exact stack needs — and handle the files that were committed before the rule existed.

Procedure

Identify the stack: languages, frameworks, build tools, editors, and OS in play. Infer what is visible from any pasted file list, and ask one batched round for the rest.
Compose the file in labeled sections: per-language build outputs and caches, per-tool artifacts, editor and OS noise, and a project-specific section for local env files and generated assets. Every non-obvious pattern gets a trailing comment saying what it ignores.
Check for the classic mistakes: ignoring lockfiles that should be committed, patterns broad enough to swallow source (a bare directory name matching everywhere), and negation rules ordered so they cannot work.
Detect the already-tracked problem: files matching the new rules that git currently tracks will keep appearing until untracked. List them and provide the untrack commands, clearly labeled as changing the repository.
Deliver in the contract below.

Deliverable format:

GITIGNORE: <stack summary>
<the .gitignore content, sectioned and commented>

Already tracked but now ignored: <files | none found>
Untrack commands (run only after review; removes from tracking, not from disk): <commands>
Deliberately NOT ignored: <lockfiles, etc. — why they stay committed>

Rules

Never ignore dependency lockfiles by default; committing them is the norm, and ignoring them is an explicit user decision.
Never emit an untrack command as if routine; it changes the repository for everyone and is labeled for review before running.
Secrets and env files are ignored AND flagged: ignoring them going forward does not un-commit what is already in history, and the note says so.

Degradation

If the stack cannot be determined, produce a minimal OS-and-editor base file plus a short question list, rather than a kitchen-sink file that hides real problems in noise.

Like this? This is the free gateway skill for Git Wizard by Moltline Studio. The paid listing: https://www.agensi.io/skills/git-wizard-bundle

---name: git-wizarddescription: Build a correct .gitignore for your exact stack, and clean up files already tracked by mistake. Use when starting a repo or when build artifacts keep showing up in diffs.---# Gitignore Builder*Free gateway skill from the Git Wizard bundle by GarphenGate.*Build the .gitignore your exact stack needs — and handle the files that were committed before the rule existed.## Procedure1. Identify the stack: languages, frameworks, build tools, editors, and OS in play. Infer what is visible from any pasted file list, and ask one batched round for the rest.2. Compose the file in labeled sections: per-language build outputs and caches, per-tool artifacts, editor and OS noise, and a project-specific section for local env files and generated assets. Every non-obvious pattern gets a trailing comment saying what it ignores.3. Check for the classic mistakes: ignoring lockfiles that should be committed, patterns broad enough to swallow source (a bare directory name matching everywhere), and negation rules ordered so they cannot work.4. Detect the already-tracked problem: files matching the new rules that git currently tracks will keep appearing until untracked. List them and provide the untrack commands, clearly labeled as changing the repository.5. Deliver in the contract below.Deliverable format:```GITIGNORE: <stack summary><the .gitignore content, sectioned and commented>Already tracked but now ignored: <files | none found>Untrack commands (run only after review; removes from tracking, not from disk): <commands>Deliberately NOT ignored: <lockfiles, etc. — why they stay committed>```## Rules- Never ignore dependency lockfiles by default; committing them is the norm, and ignoring them is an explicit user decision.- Never emit an untrack command as if routine; it changes the repository for everyone and is labeled for review before running.- Secrets and env files are ignored AND flagged: ignoring them going forward does not un-commit what is already in history, and the note says so.## DegradationIf the stack cannot be determined, produce a minimal OS-and-editor base file plus a short question list, rather than a kitchen-sink file that hides real problems in noise.---*Like this? This is the free gateway skill for **Git Wizard** by Moltline Studio. The paid listing: https://www.agensi.io/skills/git-wizard-bundle*

Frequently asked questions

Git Wizard