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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable workflow with concrete commands, a real bundled collector script, explicit validation/stop checkpoints, and clear article templates. It is slightly verbose in its inlined templates and could push more boilerplate into references, but otherwise excellent.

Suggestions

Move the full Required Article Structure and Article Outline templates into a reference file (e.g. references/article-template.md) and link to it, keeping SKILL.md as a leaner overview — this would improve both conciseness and progressive_disclosure.

The script path in step 2 is shown as a placeholder '/path/to/postgres-commit-history-article/scripts/...'; consider noting how to resolve the skill's own directory (e.g. relative to SKILL.md) so the command is truly copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and domain-specific (revert-exclusion logic, verification paths, grouping guidance) without explaining concepts Claude already knows, though the full article-structure and no-article templates add length that could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste-ready commands (`git rev-parse --show-toplevel`, the exact `collect_pg_commits.py` invocation with args, `git show -s --format=fuller`, `git log --reverse --format=...`), concrete test/doc paths, a real bundled script, and explicit filename patterns covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation checkpoints — verify PG checkout, exclude reverts, stop and return no-article analysis when no value remains, verify examples against tests/docs before writing — and feedback loops for error recovery, satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections with a single one-level-deep bundle reference (scripts/collect_pg_commits.py, which exists and is clearly signaled in step 2); the inlined article templates are integral to the workflow but make the file longer than a pure overview, a minor organization gap.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific, complete, and distinctive, with concrete actions and an explicit 'Use when' trigger clause written in third person. Its only weakness is verbosity in the trigger enumeration, which packs scenarios alongside natural phrases.

Suggestions

Trim the 'Use when' clause to the most natural user-facing triggers ('interpret Postgres commits', 'summarize a release/development window', 'provides two commit ids') and fold the rest into the body to reduce description length.

Consider adding a common synonym such as 'release notes draft' or 'changelog summary' to broaden natural trigger coverage without much length.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Analyze PostgreSQL git commit history between two commit ids', 'write a Chinese Markdown article', 'examples checked against SQL tests, docs, or relevant source', 'group related commits', 'exclude reverted commits', and a no-article fallback — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (analyze commits, write sourced article, or return no-article analysis) and when via a clear 'Use when the user is inside a PostgreSQL source checkout and provides two commit ids...' clause with concrete triggers.	5 / 5
Trigger Term Quality	Strong natural triggers ('interpret Postgres commits', 'summarize a release/development window', 'provides two commit ids', 'exclude reverted commits'), but the long enumeration mixes scenarios with natural phrases and omits a few synonyms, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A narrow niche — Postgres commit-range analysis producing a Chinese 公众号 article from a PG source checkout given two commit ids — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: digoal/blog
Path: skills/postgres-commit-history-article/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.