git-summary

What This Skill Does

The git-summary skill acts as an intelligent repository observer for OpenClaw. It automates the collection and synthesis of Git metadata, providing a high-level health check of any local project. Instead of manually running multiple terminal commands, users can invoke this skill to receive a consolidated dashboard covering branch state, recent commit history, remote configurations, and a breakdown of pending changes. It parses standard Git command output into a human-readable, structured report, making it easier for developers to get back into the flow of a project or assess the current state of a complex codebase.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/zweack/git-summary. Once installed, OpenClaw will automatically recognize the intent to summarize repository metadata whenever you request a Git status overview.

Use Cases

This skill is ideal for developers switching between multiple projects throughout the day, teams performing quick peer-review handoffs, or contributors catching up on the status of long-running feature branches. It is particularly useful for CI/CD pipeline auditing or quick sanity checks before pushing commits to a shared upstream repository. By providing a snapshot of staged versus unstaged changes, it acts as a final safety buffer to prevent accidental commits of debug code or untracked sensitive files.

Example Prompts

1. "OpenClaw, give me a quick summary of this repository so I know where I left off."
2. "What is the current status of my branch, and what have I been working on lately?"
3. "Show me the recent commit history and any uncommitted changes in this directory."

Tips & Limitations

When using git-summary, ensure you are within a directory initialized as a Git repository; otherwise, the skill will suggest running git init. Note that for extremely large monorepos, generating a full contributor list via git shortlog can be performance-intensive. We recommend running this during off-peak times in such environments. Always be mindful of your terminal output; while the skill hides sensitive tokens in URL strings, always double-check logs before sharing them with third-party stakeholders to ensure no proprietary information is accidentally leaked.