GitLog
by BytesAgain
View formatted commit history, author stats, and commit frequency patterns. Use when reviewing logs, comparing contributions, or generating repo reports.
安装
claude skill add --url github.com/openclaw/skills/tree/main/skills/ckchzh/gitlog文档
GitLog
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. Track what was fixed, the method used (amend, rebase, filter-branch), and the scope of changes. |
gitlog report <input> | Log a report entry for commit frequency analysis, contributor statistics, or release cadence summaries. Capture key metrics and trends from repository history. |
Utility Commands
| Command | Description |
|---|---|
gitlog stats | Show summary statistics across all log files, including entry counts per category and total data size on disk. |
gitlog export <fmt> | Export all data to a file in the specified format. Supported formats: json, csv, txt. Output is saved to the data directory. |
gitlog search <term> | Search all log entries for a term using case-insensitive matching. Results are grouped by log category for easy scanning. |
gitlog recent | Show the 20 most recent entries from the unified activity log, giving a quick overview of recent work across all commands. |
gitlog status | Health check showing version, data directory path, total entry count, disk usage, and last activity timestamp. |
gitlog help | Show the built-in help message listing all available commands and usage information. |
gitlog version | Print the current version (v2.0.0). |
Data Storage
All data is stored locally at ~/.local/share/gitlog/. Each domain command writes to its own log file (e.g., check.log, lint.log). A unified history.log tracks all actions across commands. Use export to back up your data at any time.
Requirements
- Bash (4.0+)
- No external dependencies — pure shell script
- No network access required
When to Use
- Verifying commit message compliance and signature validity across releases and pull requests
- Generating changelogs and release notes from commit history with contributor attribution
- Linting commit messages to enforce conventional commit standards across the team
- Comparing branch histories and tracking divergence for merge planning and conflict prevention
- Building a searchable archive of commit explanations, fixes, and format conversion records
Examples
# Log a check operation
gitlog check "Verified all 47 commits in v2.0 release are GPG-signed by authorized authors"
# Generate a changelog entry
gitlog generate "v2.0.0 changelog — 47 commits, 12 contributors, 3 breaking changes"
# Validate commit messages
gitlog validate "All 23 commits follow conventional format: feat(scope): message"
# Log a lint result
gitlog lint "Found 3 commits with missing scope in message, 1 with subject over 72 chars"
# Record a diff comparison
gitlog diff "main..feature-auth: 23 commits ahead, 5 behind, no merge conflicts detected"
# View all statistics
gitlog stats
# Export everything to CSV
gitlog export csv
# Search entries mentioning release
gitlog search release
# Check recent activity
gitlog recent
# Health check
gitlog status
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
相关 Skills
前端设计
by anthropics
面向组件、页面、海报和 Web 应用开发，按鲜明视觉方向生成可直接落地的前端代码与高质感 UI，适合做 landing page、Dashboard 或美化现有界面，避开千篇一律的 AI 审美。
✎ 想把页面做得既能上线又有设计感，就用前端设计：组件到整站都能产出，难得的是能避开千篇一律的 AI 味。
网页构建器
by anthropics
面向复杂 claude.ai HTML artifact 开发，快速初始化 React + Tailwind CSS + shadcn/ui 项目并打包为单文件 HTML，适合需要状态管理、路由或多组件交互的页面。
✎ 在 claude.ai 里做复杂网页 Artifact 很省心，多组件、状态和路由都能顺手搭起来，React、Tailwind 与 shadcn/ui 组合效率高、成品也更精致。
网页应用测试
by anthropics
用 Playwright 为本地 Web 应用编写自动化测试，支持启动开发服务器、校验前端交互、排查 UI 异常、抓取截图与浏览器日志，适合调试动态页面和回归验证。
✎ 借助 Playwright 一站式验证本地 Web 应用前端功能，调 UI 时还能同步查看日志和截图，定位问题更快。
相关 MCP 服务
GitHub
编辑精选by GitHub
GitHub 是 MCP 官方参考服务器，让 Claude 直接读写你的代码仓库和 Issues。
✎ 这个参考服务器解决了开发者想让 AI 安全访问 GitHub 数据的问题，适合需要自动化代码审查或 Issue 管理的团队。但注意它只是参考实现，生产环境得自己加固安全。
Context7 文档查询
编辑精选by Context7
Context7 是实时拉取最新文档和代码示例的智能助手，让你告别过时资料。
✎ 它能解决开发者查找文档时信息滞后的问题，特别适合快速上手新库或跟进更新。不过，依赖外部源可能导致偶尔的数据延迟，建议结合官方文档使用。
by tldraw
tldraw 是让 AI 助手直接在无限画布上绘图和协作的 MCP 服务器。
✎ 这解决了 AI 只能输出文本、无法视觉化协作的痛点——想象让 Claude 帮你画流程图或白板讨论。最适合需要快速原型设计或头脑风暴的开发者。不过，目前它只是个基础连接器，你得自己搭建画布应用才能发挥全部潜力。