AgentStack
SKILL verified MIT Self-run

Writing Git Commits

skill-emgreppi-business-central-ai-skill-writing-git-commits · by emgreppi

Writes git commit messages with proper format, type prefixes (feat/fix/chore), and imperative mood. Use when committing changes, writing a commit message, formatting commit text, or asking how to commit code properly.

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-emgreppi-business-central-ai-skill-writing-git-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 Writing Git Commits? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Skill: Git Commit Message Rules

Validation Gates

  1. Subject: Type prefix present, imperative mood, max 72 chars
  2. Body/Footer: Only if explicitly requested by user
  3. Final: No past tense, no generic messages, no file names in subject

Basic Rules

| Property | Value | |----------|-------| | Language | English | | Subject max | 72 characters | | Tone | Imperative ("add", "fix", not "added", "fixed") |

Allowed Types

| Type | Description | Example | |------|-------------|---------| | feat | New features | feat: add purchase order support | | fix | Bug fixes | fix: resolve user login issue | | chore | Non-feature (build, config) | chore: rename rental file | | refactor | Code refactoring | refactor: simplify rent logic | | deploy | Deployment changes | deploy: trigger deployment | | docs | Documentation only | docs: update starting guide |

Subject Line Format

: 

Examples:

  • feat: add customer validation on save
  • fix: correct tax amount calculation
  • refactor: extract logic to helper codeunit

Body (only if requested)

  • Do NOT include by default
  • Explain why and how, not just what
  • Wrap at ~72–100 chars
feat: add automatic token refresh for API calls

- Tokens cached with expiration tracking
- Auto-refresh 5 minutes before expiry
- Fallback to re-authentication if refresh fails

Footer (only if requested)

  • BREAKING CHANGE: describe what changed
  • Issue refs: Refs: #123, Closes: #456
feat: change API endpoint structure

BREAKING CHANGE: API endpoints now require version prefix.
Old: /api/customers → New: /api/v2.0/customers

Refs: #456

Quick Reference

Minimum (default):

feat: add customer export functionality

With body:

feat: add customer export functionality

Implements CSV export with date range filtering.

With footer:

fix: resolve duplicate entry error

Closes: #790

Do NOT

  • Use past tense ("added", "fixed")
  • Exceed 72 characters in subject
  • Include body/footer unless requested
  • Use generic messages ("fix bug", "update code")
  • Include file names in subject

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.