AgentStack
SKILL verified Apache-2.0 Self-run

Commit Message Enforcer

skill-ravisingh11-agent-safe-engineering-commit-message-enforcer · by ravisingh11

Standardize, review, and enforce enterprise-grade commit messages using Conventional Commits, scoped types, breaking-change footers, and clear history hygiene. Use when asked to harden commit messaging, review commit history, configure commitlint, or prepare clean commits.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-ravisingh11-agent-safe-engineering-commit-message-enforcer

✓ 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 Commit Message Enforcer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Commit Message Enforcer

Use this skill when creating, reviewing, or enforcing commit messages.

Format

[optional scope]: 

[optional body]

[optional footer(s)]

Commit Types

  • feat: user-visible capability.
  • fix: bug fix.
  • docs: documentation or standards.
  • ci: workflow, automation, or ruleset change.
  • chore: repository maintenance.
  • refactor: behavior-preserving code restructuring.
  • test: test-only change.
  • security: security hardening or vulnerability remediation.
  • deps: dependency update.
  • revert: revert a prior change.

Decision Rules

  • Use one primary purpose per commit. Split unrelated changes.
  • Use scopes when they add clarity, such as ci, api, web, license, skills, or a package name.
  • Use ! or a BREAKING CHANGE: footer for incompatible behavior.
  • Keep the subject imperative, lowercase after the type, and specific.
  • Put verification details in the body when the commit affects release confidence.

Verification

  • Check the staged diff matches the commit subject.
  • Confirm no generated or unrelated files are staged.
  • If enforcing in CI, validate with commitlint or an equivalent parser.

References

  • Conventional Commits baseline: references/conventional-commits.md

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.

Versions

  • v0.1.0 Imported from the upstream source.