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

Commit Changes

skill-vrallev-agent-skills-commit-changes · by vRallev

Inspect and understand the current Git working tree, then commit its staged and unstaged local changes with a clear title and why-focused description. Use whenever the user asks to commit changes, commit this work, create a git commit, or perform the commit portion of a larger push, pull-request, publish, or yeet workflow. For requests that also ask to push, publish, or create a PR, use this skil…

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

Install

$ agentstack add skill-vrallev-agent-skills-commit-changes

✓ 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-vrallev-agent-skills-commit-changes)

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

About

Commit Changes

Commit the current local work with an intentional message.

Workflow

  1. Confirm the repository, branch, and working-tree state with git status --short --untracked-files=all.
  2. Inspect staged changes with git diff --cached --stat and git diff --cached.
  3. Inspect unstaged changes with git diff --stat and git diff.
  4. Inspect relevant untracked files before staging them. Include untracked source or documentation files that belong to the local change. Do not add ignored files, secrets, credentials, build output, or unrelated artifacts.
  5. Use the current agent conversation and recent repository context to understand what the local change is doing and why. Inspect nearby code or recent commits when the diff alone is insufficient.
  6. If the working tree contains ambiguous or clearly unrelated changes that should not share a commit, ask the user before staging or committing.
  7. Stage the local changes that belong to the requested commit, including previously unstaged files.
  8. Review the staged diff and create the commit.
  9. Report the commit SHA, subject, and whether any local changes remain.
  10. If the user's request also includes pushing, publishing, or opening a pull request, stop this skill after the commit report and then continue with the appropriate publishing workflow.

Commit Message

Write a concise imperative title followed by a description paragraph or short bullet list.

The description must:

  • Explain why the change is important or helpful; prioritize the "why" over the "what".
  • Mention what changed only briefly, as context for understanding the reason.
  • Emphasize the problem solved, behavior enabled, risk reduced, or project/user benefit.
  • Wrap code references, file paths, command names, and identifiers in backticks for Markdown rendering.
  • Omit verification details such as tests, lint, formatting, or build commands.

Use a non-interactive commit command, for example:

git commit -m "Concise imperative title" -m "Explain why the change is important or helpful. Mention what changed only as needed for context, and wrap references like \`FormatCommand\` in backticks."

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.