How do I install the Git Backup skill?

Run npx skillmds@latest add lemonorangeapple/git-backup 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.

What does the Git Backup skill do?

Backup files with Git Repository. Use it if there is Git repository. It is listed under Coding & Dev Tools on SkillMD.

Is Git Backup 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 Backup?

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

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

Who published Git Backup?

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

Git Backup by lemonorangeapple — Agent Skill

Name: Git Backup
Author: lemonorangeapple

File contents

Git Backup Skill

Overview

Provides three local Git backup strategies to help users safely manage file changes.

Backup Strategies (Ask user to choose)

Strategy 1: Auto-commit every change

Use case: Important config files, sensitive data
Workflow:
1. Detect file changes
2. Automatically stage changed files
3. Generate commit message following Conventional Commits
4. Create local commit

Strategy 2: Never create commits

Use case: Temporary files, test files, large binaries
Workflow:
1. Detect file changes
2. Display change status only, no Git operations
3. User manages these files manually

Strategy 3: Ask user to create commit

Use case: Daily development work
Workflow:
1. Detect file changes
2. Display change summary
3. Ask user if they want to commit
4. Execute based on user choice

Commit Message Convention (Conventional Commits)

Format

<type>(<scope>): <description>

[optional body]

[optional footer]

Type Definitions

feat: New feature
fix: Bug fix
docs: Documentation update
style: Code formatting
refactor: Code refactoring
test: Test related
chore: Build/tool changes

Examples

feat(config): add backup schedule configuration
fix(auth): resolve login timeout issue
docs(readme): update installation steps

Error Handling

Common Issues

Git repo not exists → Prompt user to initialize repo
File conflicts → Show conflicted files, suggest resolution
Commit message too long → Auto-truncate or prompt user

Rollback Mechanism

Keep last 10 commit records
Support git reset to specific version

Usage Examples

Example 1: Config File Backup

# Strategy 1: Auto-commit
Detecting config.json change
Staging file...
Creating commit: feat(config): update backup settings

Example 2: Temporary File Handling

# Strategy 2: No commit
Detecting temp.log change
File not in version control (user chose not to commit)

Example 3: Interactive Confirmation

# Strategy 3: Ask user
Detecting src/main.py change
Change summary:
- Modified 3 functions
- Added 2 new methods

Create commit? (y/n)

---name: git-backupdescription: Backup files with Git Repository. Use it if there is Git repository.---# Git Backup Skill## OverviewProvides three local Git backup strategies to help users safely manage file changes.## Backup Strategies (Ask user to choose)### Strategy 1: Auto-commit every change- **Use case**: Important config files, sensitive data- **Workflow**: 1. Detect file changes 2. Automatically stage changed files 3. Generate commit message following Conventional Commits 4. Create local commit### Strategy 2: Never create commits- **Use case**: Temporary files, test files, large binaries- **Workflow**: 1. Detect file changes 2. Display change status only, no Git operations 3. User manages these files manually### Strategy 3: Ask user to create commit- **Use case**: Daily development work- **Workflow**: 1. Detect file changes 2. Display change summary 3. Ask user if they want to commit 4. Execute based on user choice## Commit Message Convention (Conventional Commits)### Format```<type>(<scope>): <description>[optional body][optional footer]```### Type Definitions- `feat`: New feature- `fix`: Bug fix- `docs`: Documentation update- `style`: Code formatting- `refactor`: Code refactoring- `test`: Test related- `chore`: Build/tool changes### Examples```feat(config): add backup schedule configurationfix(auth): resolve login timeout issuedocs(readme): update installation steps```## Error Handling### Common Issues1. **Git repo not exists** → Prompt user to initialize repo2. **File conflicts** → Show conflicted files, suggest resolution3. **Commit message too long** → Auto-truncate or prompt user### Rollback Mechanism- Keep last 10 commit records- Support `git reset` to specific version## Usage Examples### Example 1: Config File Backup```bash# Strategy 1: Auto-commitDetecting config.json changeStaging file...Creating commit: feat(config): update backup settings```### Example 2: Temporary File Handling```bash# Strategy 2: No commitDetecting temp.log changeFile not in version control (user chose not to commit)```### Example 3: Interactive Confirmation```bash# Strategy 3: Ask userDetecting src/main.py changeChange summary:- Modified 3 functions- Added 2 new methodsCreate commit? (y/n)```

Frequently asked questions

Git Backup