Skills Guide

Git Repository Summary

VerifiedSafe

Get a comprehensive overview of the current Git repository: status, recent commits, branches, and contributors.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/25/2026
Claude CodeCursorWindsurfCodex
#git#repository-overview#version-control#cli#status

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

This skill gathers a repository's state into a single view: current branch, recent commits, local and remote branches, remotes, and a summary of uncommitted changes.

Strengths

  • Runs a focused set of git commands (status, log, branch, remote, diff --stat) and renders them in a clear structured format
  • Covers both staged and unstaged work through git diff --stat and git diff --cached --stat
  • Optional top-10 contributor list via git shortlog for extra context on larger projects
  • Explicitly handles edge cases: non-repository directories and remote URLs that may embed tokens

Limitations

  • Read-only skill: it observes and summarizes but performs no Git actions such as commit, merge or push
  • The contributor listing can be slow on large historical repositories, which is only flagged to the user
  • Depth is capped at 10 commits and 10 contributors, so it is unsuitable for detailed history analysis
When to use it

Use it when onboarding onto an existing repository or when you need a quick snapshot of the current work state before starting a task.

When not to use it

Avoid it when you need deep history analysis, line-by-line diffs, or Git operations that modify the repository.

Security analysis

Safe
Quality score85/100

The skill only instructs running read-only git inspection commands (status, log, branch, remote, diff --stat, shortlog). No destructive operations, no network exfiltration, no credential handling beyond a note to avoid exposing token-containing URLs. Execution risk is minimal.

No concerns found

How this analysis is made

Examples

Quick repo overview
Give me a quick summary of this git repository: current branch, recent commits, branches and what's uncommitted.
Orient before starting work
I just cloned this project. Show me the repo status, the last 10 commits and who the main contributors are.
Vérifier l'état avant un commit
Fais-moi un résumé de l'état de ce dépôt : branche courante, fichiers modifiés ou indexés, et dernières commits.

name: git-summary description: Get a quick summary of the current Git repository including status, recent commits, branches, and contributors. user-invocable: true metadata: {"openclaw": {"emoji": "📊", "requires": {"bins": ["git"]}, "os": ["darwin", "linux", "win32"]}}

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-repository-summary-mrzxuqkh' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-repository-summary-mrzxuqkh/download' --output '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md.part' && mv '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md.part' '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && test -s '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-summary' && cp -R '.skill-downloads/git-repository-summary-mrzxuqkh' '.claude/skills/git-summary'

Cursor
test -f '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && test -s '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/git-summary' && cp -R '.skill-downloads/git-repository-summary-mrzxuqkh' '.cursor/skills/git-summary'

Codex
test -f '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && test -s '.skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/git-summary' && cp -R '.skill-downloads/git-repository-summary-mrzxuqkh' '.agents/skills/git-summary'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-repository-summary-mrzxuqkh'

openskills read 'git-repository-summary-mrzxuqkh'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-repository-summary-mrzxuqkh/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot