AgentStack
SKILL verified MIT Self-run

Clawbox Git Commit Push

skill-commonstackai-clawbox-clawbox-git-commit-push · by CommonstackAI

Use when the user asks to stage ClawBox changes, write a git commit, create a non-interactive commit, or push the current branch safely without mixing unrelated worktree changes.

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

Install

$ agentstack add skill-commonstackai-clawbox-clawbox-git-commit-push

✓ 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.

Are you the author of Clawbox Git Commit Push? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

ClawBox Git Commit Push

Use this skill when the task is to prepare a clean git commit and push it from the current ClawBox repository.

Read first

  • git status --short --branch
  • git diff --stat
  • git diff --cached --stat
  • Targeted git diff -- for files intended for the commit

Workflow

  1. Inspect repo state before staging anything.
  2. Confirm the requested commit scope from actual modified files, not assumptions.
  3. Stage only intended paths with git add .
  4. Create the commit with git commit -m "...".
  5. Check upstream with git rev-parse --abbrev-ref --symbolic-full-name @{u}.
  6. Use git push when upstream exists, or git push -u origin when the target is obvious.
  7. Report the commit hash, branch, and push result.

Guardrails

  • Never use destructive commands such as git reset --hard, git checkout --, rebase, or force-push unless the user explicitly asks.
  • Never stage unrelated or generated files silently.
  • Never amend a commit unless explicitly requested.
  • Prefer non-interactive git commands only.
  • Stop and ask when branch target, commit scope, or staged changes are ambiguous.

Verification

  • Run git status --short --branch before and after the commit.
  • Run git log --oneline -1 after the commit.
  • If pushed, verify the branch is no longer ahead with git status --short --branch.

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.