Sign in Publish

MCP servers Skills Toolkits Why AgentStack Sell Docs

SKILL verified MIT Self-run

Conventional Commits

skill-claude-code-community-ireland-claude-code-resources-conventional-commits · by Claude-Code-Community-Ireland

A Claude skill from Claude-Code-Community-Ireland/claude-code-resources.

— No reviews yet

0 installs

14 views

0.0% view→install

Install

$ agentstack add skill-claude-code-community-ireland-claude-code-resources-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.

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

Generate well-formatted conventional commit messages from staged changes.

Instructions

When asked to commit changes or when the user runs /commit:

Analyze staged changes using git diff --staged
Identify the type of change:

feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, no code change
refactor: Code restructuring
test: Adding/updating tests
chore: Maintenance tasks

Determine the scope (optional): The part of codebase affected
Write the message following this format:

``` ():

```

Examples

Simple feature:

feat(auth): add password reset functionality

Bug fix with body:

fix(api): handle null response from external service

The weather API occasionally returns null during maintenance windows.
Added defensive check to prevent crash and return cached data instead.

Breaking change:

feat(db)!: migrate from MySQL to PostgreSQL

BREAKING CHANGE: Database connection strings must be updated.
See migration guide in docs/migration-v2.md

Rules

Keep the first line under 72 characters
Use imperative mood ("add" not "added")
Don't end with a period
Reference issues when applicable
Add ! after type for breaking changes

Source & license

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

Author: Claude-Code-Community-Ireland
Source: Claude-Code-Community-Ireland/claude-code-resources
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.