AgentStack
SKILL verified Apache-2.0 Self-run

Git Commit Helper

skill-lc-rezende-ai-custom-skills-git-commit-helper · by lc-rezende

Generate conventional commit messages without scopes based on staged changes. Use when the user asks for commit message help, has staged changes, or is about to commit.

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

Install

$ agentstack add skill-lc-rezende-ai-custom-skills-git-commit-helper

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

About

Git Commit Helper (No Scope)

Generate conventional commit messages without a scope.

When to use this skill

  • The user asks for a commit message
  • Staged changes exist
  • The user is about to run git commit
  • The user mentions conventional or semantic commits

Workflow

  1. Review staged files and the staged diff.
  2. Identify the primary change type and any breaking changes.
  3. Draft a commit message using the format below.
  4. Provide a short rationale and ask if the user wants adjustments.

Commit format (no scope)

: 

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Formatting only (no logic change)
  • refactor: Code restructuring without behavior change
  • perf: Performance improvements
  • test: Test additions or fixes
  • build: Build system or tooling changes
  • ci: CI/CD pipeline changes
  • chore: Maintenance tasks

Subject checklist

  • Imperative mood ("add", "fix", "update")
  • 50-72 characters max
  • No trailing period
  • Describes what and why, not how
  • Lowercase after the type

Breaking changes

If the change is breaking, include a footer:

BREAKING CHANGE: 

Examples

Feature

feat: add jwt authentication for api requests

- implement token validation middleware
- add login and refresh endpoints

Closes #42

Fix

fix: prevent memory leak in user list

Clean up subscriptions when the component unmounts.

Refactor

refactor: extract repository layer for database access

No functional changes. Improves testability and separation.

Breaking change

feat: update user api response structure

BREAKING CHANGE: response is now { data, metadata }.

Output expectations

  • Provide the recommended commit message in full.
  • Explain the chosen type and any breaking change rationale.

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.