GitLog
View formatted commit history, author stats, and commit frequency patterns. Use when reviewing logs, comparing contributions, or generating repo reports.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ckchzh/gitlogGitLog
GitLog v2.0.0 — a developer toolkit for managing commit history and log analysis from the command line. Log checks, validations, changelog generations, lint results, diffs, and more. Each entry is timestamped and persisted locally. Works entirely offline — your data never leaves your machine.
Why GitLog?
- Works entirely offline — your data never leaves your machine
- Simple command-line interface with no GUI dependency
- Export to JSON, CSV, or plain text at any time for sharing or archival
- Automatic activity history logging across all commands
- Each domain command doubles as both a logger and a viewer
Commands
Domain Commands
Each domain command works in two modes: log mode (with arguments) saves a timestamped entry, view mode (no arguments) shows the 20 most recent entries.
| Command | Description |
|---|---|
gitlog check <input> | Log a check operation such as verifying commit signatures, author consistency, or branch protection compliance. Track verification outcomes across releases and branches. |
gitlog validate <input> | Log a validation entry for commit message format checks, conventional commit compliance, or PR title standards. Record pass/fail outcomes and specific violations found. |
gitlog generate <input> | Log a generation task for changelog creation, release notes drafting, or commit summary generation. Track what was generated, the commit range covered, and contributor counts. |
gitlog format <input> | Log a formatting operation for reformatting log output, adjusting date formats, or restructuring commit displays. Record the format changes applied and the resulting output style. |
gitlog lint <input> | Log a lint result identifying commits with missing scopes, non-standard prefixes, or overly long subject lines. Useful for enforcing consistent commit message quality across teams. |
gitlog explain <input> | Log an explanation entry documenting why specific commits were made, architectural decisions behind changes, or context for complex merges. Build an annotated history. |
gitlog convert <input> | Log a conversion task for transforming log formats between representations such as markdown changelogs, HTML release pages, or RSS feeds. Record source and target formats. |
gitlog template <input> | Log a template operation for creating commit message templates, PR description templates, or changelog section templates. Track template versions and adoption. |
gitlog diff <input> | Log a diff result comparing branches, tags, or time ranges. Record commits ahead/behind, divergence points, and merge conflict potential between branches. |
gitlog preview <input> | Log a preview entry for reviewing staged commits, upcoming release contents, or draft changelogs before publishing. Useful for pre-release audits. |
gitlog fix <input> | Log a fix operation for commit message rewrites, author corrections, or history cleanup. |
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ckchzh-gitlog": {
"enabled": true,
"auto_update": true
}
}
}Tags
Related Skills
daily-report-generator
Automatically generate daily/weekly work reports from git commits, calendar events, and task lists. Use when you need to quickly create professional work reports without manual effort.
git-mender
git-mender — Automatically fix GitHub issues end-to-end: reads the issue, analyzes repository code, implements a fix, and submits a pull request. Use when the user provides a GitHub issue URL, mentions fixing a GitHub issue, or uses the /fix-issue command. Supports URLs in the format https://github.com/{owner}/{repo}/issues/{number}.
vibe-coding-checker
描述一个功能或项目，AI 快速评估用 Cursor/Windsurf/Bolt 等 AI 编程工具能否独立实现， 给出可行性判断、推荐工具、拆解路径和风险提示。
issue-to-pr
issue-to-pr — Automatically fix GitHub issues end-to-end: reads the issue, analyzes repository code, implements a fix, and submits a pull request. Use when the user provides a GitHub issue URL, mentions fixing a GitHub issue, or uses the /fix-issue command. Supports URLs in the format https://github.com/{owner}/{repo}/issues/{number}.
changelog-curator
从变更记录、提交摘要或发布说明中整理对外 changelog，并区分用户价值与内部改动。；use for changelog, release-notes, docs workflows；do not use for 捏造未发布功能, 替代正式合规审批.