agentleFS
Sign inStart free
lemonorangeapplelemonorangeapple/JuneAgent/skills/git-backup/SKILL.md

git-backup

Skill1 starsChanged 3 months agoMITView on GitHub

Backup files with Git Repository. Use it if there is Git repository.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. THEROCKSSS/hermes-skills-portfolio★ 1same name
    2. kai-chop/claude-config-lifeboat★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask user if they want to commit

    line 33
  2. Distinctive:

    Keep last 10 commit records

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Git repo not exists → Prompt user to initialize repo
  2. File conflicts → Show conflicted files, suggest resolution
  3. 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free