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

Commit

skill-konh-claudetools-commit · by KonH

Create a git commit for the staged changes, branching off the default branch first if needed

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

Install

$ agentstack add skill-konh-claudetools-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-konh-claudetools-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

Create a git commit for the staged changes.

Pre-commit step: branch selection

Before committing, check the current branch:

  1. git branch --show-current
  2. Determine the repository's default branch (main or master — e.g. via git symbolic-ref --short refs/remotes/origin/HEAD, falling back to whichever of main/master exists locally).
  3. If the current branch is the default branch: create and switch to a new branch via git checkout -b feature/, where ` is a meaningful slug derived from the change being committed (e.g. feature/province-division-config`). Do this before staging/committing anything else.
  4. If it is anything other than the default branch (i.e. already on a feature branch or other non-default branch): leave the branch as-is — do not create or switch branches.

Rules

  • Subject line: short, imperative, no period
  • Explain why, not what — the diff already shows what changed
  • No bullet-point summaries of changed files
  • Always add a Co-Authored-By trailer for the model in use, e.g. Co-Authored-By: Claude Fable 5

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.