Reddi Git Summary

reddi.tech fork of git-summary. Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 22 · 0 current installs · 0 all-time installs
byNissan Dookeran@nissan
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description promise a local Git repository summary and the instructions only require the git binary and run git commands (status, log, branch, remote, diff, shortlog) — all directly related to the stated purpose.
Instruction Scope
SKILL.md instructs the agent to execute standard, non-network git commands against the current repo and to present results in a structured format. It does not request reading unrelated files, accessing unrelated env vars, or sending data to external endpoints. It explicitly notes sensitivity around URLs/tokens.
Install Mechanism
No install spec or code is included — the skill is instruction-only and relies on an existing git binary, which is the lowest-risk pattern for skills.
Credentials
The skill requires no environment variables, credentials, or config paths. The requested capabilities (git binary access) are proportionate to a repository-summary task.
Persistence & Privilege
always:false and no install or self-modifying behavior. Autonomous invocation is allowed (platform default) but the skill does not request persistent privileges or modify other skills/config.
Assessment
This skill appears safe and does what it says: run standard git commands in the current working directory and format the output. Before installing or invoking it, be aware that: (1) it will run against whatever repository the agent is placed in, so in private/confidential repos it will read commit history, branch names, and remote URLs (which may contain sensitive information); (2) ensure the runtime has git installed; and (3) because it is instruction-only, there is no bundled code to review — review the SKILL.md to confirm the exact commands you’re comfortable with. If you plan to use it on sensitive repositories, consider running it in a controlled environment or reviewing output formatting rules to avoid exposing tokens/URLs.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.2
Download zip
latestvk97cfkrh47ynehs8ns7a304ves82y83a

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📊 Clawdis
OSmacOS · Linux · Windows
Binsgit

SKILL.md

Git Summary Skill

This skill provides a comprehensive overview of the current Git repository state.

Usage

When the user asks for a git summary, repository overview, or wants to understand the current state of a git project, use the terminal to run the following commands and present the results in a clear, organized format.

Instructions

  1. Repository Status: Run git status --short --branch to get the current branch and working directory status.

  2. Recent Commits: Run git log --oneline -10 --decorate to show the last 10 commits with branch/tag decorations.

  3. Branch Overview: Run git branch -a --list to list all local and remote branches.

  4. Remote Info: Run git remote -v to show configured remotes.

  5. Uncommitted Changes Summary:

    • Run git diff --stat for unstaged changes
    • Run git diff --cached --stat for staged changes
  6. Contributors (optional, for larger context): Run git shortlog -sn --all | head -10 to show top 10 contributors.

Output Format

Present the gathered information in a structured format:

## 📊 Git Repository Summary

### Current Branch & Status
- Branch: `<branch_name>`
- Status: <clean/dirty with X modified, Y staged, Z untracked>

### Recent Commits (Last 10)
<formatted commit list>

### Branches
- Local: <count> branches
- Remote: <count> branches
<list notable branches>

### Remotes
<list remotes with URLs>

### Uncommitted Changes
<summary of staged and unstaged changes>

Notes

  • If not in a git repository, inform the user and suggest initializing one with git init.
  • For large repositories, the contributor list may take a moment - warn the user if this is expected.
  • Always respect that some information may be sensitive - don't expose full URLs if they contain tokens.

Files

3 total
Select a file
Select a file to preview.

Comments

Loading comments…