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

Commit

skill-nweii-agent-stuff-commit · by nweii

Create well-formatted commits with conventional commit messages. Use when user asks to commit, wants to commit changes, or needs help with commit messages.

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

Install

$ agentstack add skill-nweii-agent-stuff-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 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.

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-nweii-agent-stuff-commit)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo 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

Create well-formatted git commits following Conventional Commits.

Format

[optional scope]: 

[optional body]

[optional footer(s)]

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only
  • style: Formatting, missing semi-colons, etc. (no code change)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Performance improvement
  • test: Adding missing tests
  • chore: Maintenance tasks (build process, dependencies, etc.)

Guidelines

  • Subject line: Imperative mood ("add", not "added"); aim for ≤50 characters.
  • Body: Wrap at 72; explain what and why, not how.
  • Scope: Optional, indicates section of codebase (e.g., feat(auth):).
  • Breaking changes: Add ! after type/scope (e.g., feat!:) and explain in footer.

Process

  1. Review staged changes (git diff --staged) and outstanding git status.
  2. Stage files explicitly when there's any chance git add -A would sweep in secrets or unrelated work.
  3. Pick the type and scope that fit.
  4. Write a concise subject; add a body when the change isn't self-explanatory.

Examples

feat(auth): add OAuth2 login support

Implements Google and GitHub OAuth providers.
Closes #123
fix: resolve race condition in data fetcher

The previous implementation could return stale data
when multiple requests were in flight.
chore: update dependencies to latest versions

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.