Clawbox Git Commit Push
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.
Install
$ agentstack add skill-commonstackai-clawbox-clawbox-git-commit-push ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-commonstackai-clawbox-clawbox-git-commit-push) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →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 --branchgit diff --statgit diff --cached --stat- Targeted
git diff --for files intended for the commit
Workflow
- Inspect repo state before staging anything.
- Confirm the requested commit scope from actual modified files, not assumptions.
- Stage only intended paths with
git add. - Create the commit with
git commit -m "...". - Check upstream with
git rev-parse --abbrev-ref --symbolic-full-name @{u}. - Use
git pushwhen upstream exists, orgit push -u originwhen the target is obvious. - 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 --branchbefore and after the commit. - Run
git log --oneline -1after 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.
- Author: CommonstackAI
- Source: CommonstackAI/ClawBox
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.