How do I install the Git Add skill?

Run npx skillmds@latest add majiayu000/git-add-2 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 Add safe to use?

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

Which AI agents work with Git Add?

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 Add free to use?

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

Who published Git Add?

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

Git Add by majiayu000 — Agent Skill

Name: Git Add
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Agent protocol: Stage atomic git changes

Goal: Stage a single, cohesive set of related file changes for an atomic commit.

When: Use when the agent wants to stage selected files for a git commit.

NOTE: Use this skill only for staging selected files, but not committing them.

Primary directives

Study references/ files ONLY if more than one file exists to stage.
NEVER use git add . or git add -A.
NEVER use git checkout or git restore.
Assume a file in both staged and unstaged states needs staging.
Stage files explicitly: git add <file1> <file2> ....
Leave unrelated changes unstaged.
Isolate .gitignore changes; stage them in a separate commit.
Except for .gitignore, DON'T edit any files

Git directives

Git commands (use --no-pager and --no-ext-diff for diffs):

For `unstaged` changes

git --no-pager diff --no-ext-diff --stat --minimal --patience --histogram \
    --find-renames --summary --no-color -U10 <file_group>

For staged changes

git --no-pager diff --staged --no-ext-diff --stat --minimal --patience \
    --histogram --find-renames --summary --no-color -U10

For repository status

git status --porcelain=v2 --branch

For staging files

git add <file1> <file2> ...

Efficiency directives

Single-file shortcut: If one tracked unstaged file, stage immediately (skip reference study)
Batch git operations on file groups, avoid individual file processing
Use parallel execution when possible
Analyze tracked files via git diff; read non-ignored untracked files; omit ignored files
Reduce token usage

Task management

For complex tasks: use todo system to break down, plan, and optimize workflow.

Workflow

Exception: If exactly one tracked unstaged file exists, stage it immediately and skip steps below.

Study references files
Review repository status to identify all modified/new/untracked files
Update .gitignore following reference guidelines
Select smallest group of unstaged files forming single logical change
Stage the atomic group
Output status as first line, then bullet list of staged files

Output

Files modified:

Staging area - Files added to git staging area

Status communication:

First line of output indicates status:

SUCCESS: staged N files for atomic commit - Files staged successfully
WARN: no files available to stage - No unstaged changes found
ERROR: [message] - Failed to stage files

Following lines (when SUCCESS): bullet point list of staged files

---name: git-add-2description: Autonomously select files to stage for an atomic Git commit. Use when the agent wants to stage selected files for a git commit. Only stages selected files, but does not commit them.---# Agent protocol: Stage atomic git changes**Goal:** Stage a single, cohesive set of related file changes for anatomic commit.**When:** Use when the agent wants to stage selected files for a gitcommit.**`NOTE`:** _Use this skill only for staging selected files, but notcommitting them._## Primary directives- Study `references/` files `ONLY` if more than one file exists to stage.- **`NEVER`** use `git add .` or `git add -A`.- **`NEVER`** use `git checkout` or `git restore`.- Assume a file in both `staged` and `unstaged` states needs staging.- Stage files explicitly: `git add <file1> <file2> ...`.- Leave unrelated changes `unstaged`.- Isolate `.gitignore` changes; stage them in a separate commit.- Except for `.gitignore`, **`DON'T`** edit any files## Git directivesGit commands (use `--no-pager` and `--no-ext-diff` for diffs):### For `unstaged` changes```bashgit --no-pager diff --no-ext-diff --stat --minimal --patience --histogram \ --find-renames --summary --no-color -U10 <file_group>```### For staged changes```bashgit --no-pager diff --staged --no-ext-diff --stat --minimal --patience \ --histogram --find-renames --summary --no-color -U10```### For repository status```bashgit status --porcelain=v2 --branch```### For staging files```bashgit add <file1> <file2> ...```## Efficiency directives- Single-file shortcut: If one tracked `unstaged` file, stage immediately (skip reference study)- Batch git operations on file groups, avoid individual file processing- Use parallel execution when possible- Analyze tracked files via `git diff`; read non-ignored `untracked` files; omit ignored files- Reduce token usage## Task managementFor complex tasks: use `todo` system to break down, plan, and optimizeworkflow.---## Workflow**Exception:** If exactly one tracked `unstaged` file exists, stage itimmediately and skip steps below.1. Study references files2. Review repository status to identify all modified/new/`untracked` files3. Update `.gitignore` following reference guidelines4. Select smallest group of `unstaged` files forming single logical change5. Stage the atomic group6. Output status as first line, then bullet list of staged files## Output**Files modified:**- Staging area - Files added to git staging area**Status communication:**First line of output indicates status:- `SUCCESS: staged N files for atomic commit` - Files staged successfully- `WARN: no files available to stage` - No `unstaged` changes found- `ERROR: [message]` - Failed to stage files**Following lines (when SUCCESS):** bullet point list of staged files

Frequently asked questions

Git Add