postgres-commit-history-article
Analyze PostgreSQL git commit history between two commit ids and, when valuable DBA/application-developer changes exist, write a Chinese Markdown article for WeChat/公众号 readers with examples checked against SQL tests, docs, or relevant source. Use when the user is inside a PostgreSQL source checkout and provides two commit ids, asks to interpret Postgres commits, summarize a release/development window, identify DBA/application-developer value from commit logs, group related commits, exclude reverted commits, and either output a sourced article under the current project's markdown directory or return a no-article analysis when no valuable commits are present.
Best for Chinese technical content c…Works with GitHub
⌘source
- author
@digoal- repo
- digoal/blog
- language
- HTML
★8.5kstars
1.9kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Analyzes PostgreSQL commit history between two commit IDs
- ·Writes Chinese Markdown articles for WeChat/公众号 readers
- ·Filters for DBA and application-developer valuable changes
- ·Groups related commits and excludes reverted ones
- ·Verifies examples against SQL tests, docs, or source
- ·Outputs article or no-article analysis
Use Cases
- →Summarizing PostgreSQL release changes for Chinese developer audiences
- →Documenting development window changes for DBA teams
- →Creating educational content from PostgreSQL commit history
- →Analyzing git history to identify user-facing improvements
Best for
- ✓Chinese technical content creators
- ✓PostgreSQL community maintainers
- ✓DBA teams tracking database changes
Not ideal for
- !One-off commit analysis
- !Non-Chinese audiences
- !Code review without documentation needs
FAQs
name
postgres-commit-history-article
description
Analyze PostgreSQL git commit history between two commit ids and, when valuable DBA/application-developer changes exist, write a Chinese Markdown article for WeChat/公众号 readers with examples checked against SQL tests, docs, or relevant source. Use when the user is inside a PostgreSQL source checkout and provides two commit ids, asks to interpret Postgres commits, summarize a release/development window, identify DBA/application-developer value from commit logs, group related commits, exclude reverted commits, and either output a sourced article under the current project's markdown directory or return a no-article analysis when no valuable commits are present.
Postgres Commit History Article
Goal
Turn a PostgreSQL commit range into a publishable Chinese Markdown article for DBA and application developers when the range contains valuable user-facing or operator-facing changes. Work from commit logs first, then only deep-read full commit messages for selected valuable groups. Before writing usage examples, inspect relevant SQL tests, documentation, or source context so examples are rich and correct. Do not analyze code diffs unless needed to understand a mechanism or produce a practical example.
Inputs
Expect the user to run the skill from a PostgreSQL git checkout and provide:
commitid1 commitid2
Treat the range as inclusive of both endpoints. If the order is unclear, test both ancestry directions and use the direction that produces a valid range; otherwise ask for clarification.
Workflow
-
Verify context.
- Confirm
git rev-parse --show-toplevelsucceeds. - Confirm the repository looks like PostgreSQL, for example
src/backend,src/include, andconfigure.acexist. - Create
markdown/in the current project if missing.
- Confirm
-
Collect commit metadata without diffs.
$install
1-click copynpx skills add digoal/blog --skill postgres-commit-history-articleSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.