skill-dianyike-claude-code-insights-commit-style · by Install
$ agentstack add skill-dianyike-claude-code-insights-commit-style ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dianyike-claude-code-insights-commit-style) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Commit Message Style
Format
- Sentence case: capitalize the first letter only
- Verb-led: start with an imperative verb (see the verb table below)
- Single line: no body or footer unless the user explicitly asks for one
- No type prefix: do not use conventional-commits
type:ortype(scope):format - Concise: aim for under 72 characters
Why: This matches the project's existing git history. Consistent verb-led messages make git log --oneline scannable without extra ceremony.
Parallel items
Use commas to list related changes in one commit:
Consolidate rules: add examples, merge TDD/error sections, reduce overlapA colon separates the high-level intent from the details when a commit touches multiple concerns.
Common verbs and when to use them
| Verb | Use when | |------|----------| | Add | Introducing something new | | Fix | Correcting broken behavior | | Update | Changing existing content or config | | Remove | Deleting code, files, or features | | Refactor | Restructuring without behavior change | | Rework | Significant redesign of an existing piece | | Standardize | Making things consistent | | Harden | Strengthening security or robustness | | Trim | Removing unnecessary parts |
Scope
This skill applies only when the user asks for a commit. Claude does not create commits unsolicited (see workflow.md). The format here applies to commit subjects — not PR titles, branch names, or tag annotations unless the user asks for consistency.
Gotchas
- Do not append
🤖 Generated with Claude Codefooters orCo-Authored-By:trailers unless the user explicitly requests them — the project's git log is clean and this repo's convention is trailer-free - When unsure of tone or verb choice, run
git log --oneline -20and mirror recent style rather than guessing - The verb table is a starting set, not exhaustive — pick a better-fitting imperative verb when the listed ones don't match the change
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dianyike
- Source: dianyike/claude-code-insights
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.