SkillAgentSearch skills...

git

Execute safe Git operations and workflows including branch creation with fork sync, compliant commits, reading gitignored files, status checks, diff reviews, and history

Install / Use

npx skills add rancher/terraform-provider-rancher2 --skill git

Installs into whichever agent you are using.

About this skill
♊

Gemini Rules

Gemini CLI config

Quality Score

76/100

Category

Automation

Supported Platforms

Gemini CLI

Our assessment of git

git scores 76/100 on our quality scale, 2549th of 2,790 Automation skills we index.

Its Gemini Rules is 5.0 KB long, well organised into 11 sections with 7 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so git is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

git compared with similar skills

All 4 of these similar skills score higher than git; compare them before choosing.

SkillScoreStarsUpdatedFormat
git (this skill)by rancher7603d agoGemini Rules
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install git?
Run npx skills add rancher/terraform-provider-rancher2. The install tabs above show the steps for each supported agent.
Which AI agents does git work with?
It is written for Gemini CLI, as a Gemini Rules file. Other agents that read the same format can often use it too.
Is git safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is git still maintained?
The repository was last updated 3 days ago, so git is actively maintained.

name: git description: Execute safe Git operations and workflows including branch creation with fork sync, compliant commits, reading gitignored files, status checks, diff reviews, and history. Use whenever agents need to interact with git or inspect repository changes.

Git Management and Safe Operations

Overview

The git skill provides a safe, curated, and standardized set of Git utilities for agents written in JavaScript using simple-git. It protects against accidental state corruption, prevents commits directly to main/master, ensures commit messages comply with Conventional Commits and product boundaries, allows reading gitignored files (unless excluded by .aiexclude), and prevents unintended staging.

Rule: You should always prefer using the scripts in this skill over running raw, direct git commands (such as git diff, git status, git commit, git checkout, etc.) to interact with repository state.

Universal Options & Script Discovery

  • Help Option (-h, --help): Every script in this skill supports -h and --help. Whenever you need to discover available arguments, positional parameters, or flags for any script, execute it with --help instead of reading the source file:
    node ./scripts/<script_name>.js --help
    

Core Tasks

1. Check Workspace and Branch Status

  • Working Tree & Branch Status: View uncommitted changes and list files changed in the current branch compared to the base branch (main, master, or specified -b base-branch):
    node ./scripts/get_files_changed.js [-b base-branch]
    
  • List Modified/Untracked Paths: Get a clean list of explicit file paths that have been modified or are untracked:
    node ./scripts/get_modified_paths.js
    
  • Inspect Staged Files in Index: Inspect what files are currently staged, their stage slot (0 for normal, 1-3 for merge conflicts), and their cached diff status (A, M, D, etc.), or retrieve just file names with --name-only:
    node ./scripts/get_staged_files.js [--name-only]
    

2. Review Detailed Diffs

  • Uncommitted Changes (Staged & Unstaged): View a full diff of local changes in the working directory and staging area, optionally filtering by specific files, scoping to --staged or --unstaged, or requesting a compact summary with --stat or --name-only:
    node ./scripts/get_diff_to_review.js [--staged|--unstaged] [--stat|--name-only] [file_path...]
    
  • Branch Changes: View all changes introduced in the current branch relative to the base branch (main, master, or specified -b base-branch), optionally filtering by specific files or requesting a compact summary with --stat or --name-only:
    node ./scripts/get_branch_changes.js [--stat|--name-only] [-b base-branch] [file_path...]
    

3. Read Files Ignored by .gitignore

To safely read files that are ignored by .gitignore (such as plans, reports, or local configurations) while ensuring repository .aiexclude privacy boundaries are strictly respected:

node ./scripts/read-ignored-file.js <file_path> [start_line] [end_line]

4. Branch Management

  • Create New Branch (with Fork Upstream Sync): Syncs the local base branch (main or master) from the upstream remote before creating and checking out a new feature branch:
    node ./scripts/create-branch.js <branch-name> [base-branch]
    
  • Switch Branch: Safely switches between existing local or remote branches:
    node ./scripts/switch-branch.js <branch-name>
    

5. Staging and Unstaging Changes

To stage specific modified files while ensuring files blocked by .aiexclude cannot be accidentally staged:

node ./scripts/stage-files.js <file1> [file2...]

To stage all modified tracked files:

node ./scripts/stage-files.js --all

To stage all modified tracked files and untracked files (excluding gitignored files):

node ./scripts/stage-files.js --all --include-untracked

To unstage specific files from the staging index:

node ./scripts/unstage-files.js <file1> [file2...]

To unstage all staged changes:

node ./scripts/unstage-files.js --all

6. Create Compliant Commits

To create a commit that blocks commits to main/master, validates against Conventional Commits, verifies product boundary semver rules (changes outside internal/ cannot use feat or !), and runs spell checks:

node ./scripts/commit.js -m "fix: your commit message"

7. View Commit Log and File History

  • View Recent Commits: View a concise, color-stripped oneline commit history on the current branch or scoped to a specific file or branch:
    node ./scripts/get_commit_log.js [-n limit] [-f file] [-b branch]
    
  • Retrieve Deleted/Historical File Contents: Retrieve contents of a deleted or historical file from Git history at the latest commit or a specific revision/commit SHA:
    node ./scripts/get_deleted_file.js <file_path> [commit_or_rev]
    

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
Updated3d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low