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

Commit

skill-eeshansrivastava89-skills-commit · by eeshansrivastava89

Create a git commit with conventional message format

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

Install

$ agentstack add skill-eeshansrivastava89-skills-commit

✓ 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 Used
  • 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-eeshansrivastava89-skills-commit)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo 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 Commit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Commit Workflow

Create a focused git commit with a conventional message.

Steps

  1. Run git status to see all changes
  2. Run git diff --staged to see staged changes
  3. Run git diff to see unstaged changes
  4. Analyze changes and draft commit message:
  • Summarize what changed (not how)
  • Use imperative mood ("Add feature" not "Added feature")
  • Keep first line under 50 characters
  • Add body if needed for context
  1. Show proposed commit message and ask for approval
  2. If approved:
  • Stage relevant files (git add)
  • Create commit with the message
  • Show result

Commit Message Format

: 

Types

  • feat: New feature
  • fix: Bug fix
  • refactor: Code change that neither fixes nor adds
  • docs: Documentation only
  • test: Adding or fixing tests
  • chore: Maintenance, dependencies, config

Rules

  • Never commit without explicit user approval
  • Never use --force or destructive operations
  • Don't commit secrets, credentials, or .env files
  • Keep commits focused (one logical change)

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.