AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Conventional Commits

skill-hankunpeng-skills-conventional-commits · by hankunpeng

Enforce, validate, lint, and manage Conventional Commits across git repositories. Generates semantic changelogs and installs git hooks. Use this skill whenever the user mentions commit messages, commit conventions, conventional commits, semantic versioning, changelogs, commit linting, git hooks for commits, or wants to standardize their commit format — even if they don't explicitly say "conventio…

↗ Repository
— No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-hankunpeng-skills-conventional-commits

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-hankunpeng-skills-conventional-commits)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Conventional Commits? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Conventional Commits Skill

This skill enforces, validates, and manages Conventional Commits inside repositories.

When to Use This Skill

  • Writing commit messages: Format the user's changes as a proper Conventional Commit message.
  • Linting commits: Run scripts/commit-lint.sh to validate a commit message.
  • Generating changelogs: Run scripts/generate-changelog.sh to produce a grouped changelog from git history.
  • Installing hooks: Run scripts/install-git-hook.sh to set up automatic commit message linting in a repository.

Core Message Format

[optional scope][optional !]: 

[optional body]

[optional footer(s)]

Types

  • feat: A new feature for the user.
  • fix: A bug fix for the user.
  • docs: Documentation changes.
  • style: Formatting changes that do not affect code meaning.
  • refactor: Code changes that neither fix a bug nor add a feature.
  • perf: Code changes that improve performance.
  • test: Adding or correcting tests.
  • build: Changes affecting build systems or external dependencies.
  • ci: Changes to CI configuration scripts.
  • chore: General maintenance.
  • revert: Reverts a previous commit.

Scope

The optional scope provides additional context, enclosed in parentheses after the type. Scopes should be lowercase and may contain letters, numbers, hyphens, and underscores (e.g., feat(auth), fix(api-client)).

Breaking Changes

A breaking change is indicated by appending ! after the type/scope and before the colon:

feat(api)!: remove deprecated endpoints

Alternatively, include a BREAKING CHANGE: footer in the message body.

Footers

Footers follow the format : or #, one per line:

feat(auth): add OAuth2 support

Implements the full OAuth2 authorization code flow.

BREAKING CHANGE: removed legacy session-based auth
Refs #1234
Reviewed-by: Alice

Examples

Example 1 — Simple feature:

feat(auth): add email verification

Example 2 — Bug fix with scope:

fix(parser): handle empty input without crash

Example 3 — Breaking change with body and footer:

refactor(api)!: rename user endpoints

All /v1/user/* endpoints have been moved to /v2/users/*.

BREAKING CHANGE: /v1/user/* endpoints no longer exist
Refs #567

Example 4 — Invalid (missing type):

added new login page

Scripts Included

  • scripts/commit-lint.sh: Checks if a commit message conforms to the Conventional Commits regex.
  • scripts/install-git-hook.sh: Installs a commit-msg git hook into a target repository to automatically run the lint script on commit.
  • scripts/generate-changelog.sh: Parses git history and generates grouped Changelogs.

Usage

Linting a commit message

To lint a message, pass the message text or a file containing the message:

/scripts/commit-lint.sh "feat(auth): add email verification"

Installing the git hook in a repository

/scripts/install-git-hook.sh /path/to/repository

Generating a Changelog

/scripts/generate-changelog.sh HEAD~5..HEAD

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in Search