📊 Git Summary OpenClaw Skill - ClawHub
Do you want your AI agent to automate Git Summary workflows? This free skill from ClawHub helps with git & github tasks without building custom tools from scratch.
What this skill does
Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.
Install
npx clawhub@latest install git-summaryFull SKILL.md
Open original| name | description | user invocable |
|---|---|---|
| git-summary | Get a quick summary of the current Git repository including status, recent commits, branches, and contributors. | true |
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
-
Repository Status: Run
git status --short --branchto get the current branch and working directory status. -
Recent Commits: Run
git log --oneline -10 --decorateto show the last 10 commits with branch/tag decorations. -
Branch Overview: Run
git branch -a --listto list all local and remote branches. -
Remote Info: Run
git remote -vto show configured remotes. -
Uncommitted Changes Summary:
- Run
git diff --statfor unstaged changes - Run
git diff --cached --statfor staged changes
- Run
-
Contributors (optional, for larger context): Run
git shortlog -sn --all | head -10to 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.