Git Commit Helper

I took a look at your git-commit-helper skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 79/100, solid C-grade territory. This is based on Anthropic's Claude Skills best practices rubric. Your Writing Style is chef's kiss (10/10) — the instructions are clear and imperative without being preachy. But Progressive Disclosure Architecture is dragging you down (16/30). The skill does what it promises, which is great, but the structure needs work.

What's Working Well

• Exceptional documentation clarity — Your commit checklist, guidelines breakdown, and before/after examples are genuinely useful and easy to follow. The numbered workflow steps work.
• Real utility — You're solving an actual problem developers face (crappy commit messages), and your templates give people tangible leverage.
• Consistent voice — No marketing fluff, no second-person "you should" stuff. Just actionable guidance.
• Strong examples — The good/bad commit message comparisons and the conventional commits reference give people something to actually work with.

The Big One: Your Architecture is Too Linear

Here's the thing: All 210 lines are crammed into a single SKILL.md file. For a skill this detailed, that's a lot to load at once. Users don't need all that depth upfront.

Why it matters: Progressive Disclosure means showing people what they need when they need it. Right now, your metadata, guidelines, checklist, templates, and examples are all competing for attention in one wall of text.

The fix:

• Keep SKILL.md lean — frontmatter + trigger description + quick workflow
• Create references/commit-guidelines.md — Move your detailed commit style guidel...