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

Commit Unstaged

skill-jtsternberg-claude-plugins-commit-unstaged · by jtsternberg

Review unstaged changes, stage the intended files explicitly, and create a commit with a supplied or concise conventional message.

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

Install

$ agentstack add skill-jtsternberg-claude-plugins-commit-unstaged

✓ 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-jtsternberg-claude-plugins-commit-unstaged)

Reliability & compatibility

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

About

Commit Unstaged Changes

Use this skill only when the user explicitly asks to stage and commit their current changes.

Arguments provided: $ARGUMENTS

Codex: if the invocation text above is not populated, use a commit message supplied after the skill name or in the current request. If none is available, infer the message from the diff.

Workflow

  1. Inspect the repository state with git status, git diff, and git diff --cached.
  2. Identify the files that belong in this commit. Do not use git add -A or git add .; stage each intended file by explicit path.
  3. Stop if the intended files include secrets or private configuration (for example .env, credential files, tokens, or private keys). Do not stage them.
  4. Review the staged diff. If it contains unrelated changes, unstage the unrelated paths or ask the user to split the work before committing.
  5. Respect a commit message supplied by the user. Otherwise, derive a concise conventional commit message from the staged diff and the repository's recent commit style (git log).
  6. Create the commit. Do not amend, use --no-verify, or push unless the user explicitly asks.
  7. Report the commit hash and the remaining git status state.

If there are no unstaged changes, say so and do not create an empty commit.

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.