Clawbox git commit push

Skill CommonstackAI/ClawBox/.agents/skills/clawbox-git-commit-push

ClawBox provides a guided setup experience and unified dashboard for OpenClaw-powered agents.

Install

npx -y skills add CommonstackAI/ClawBox --skill clawbox-git-commit-push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

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 -- <paths> 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 <paths>.
Create the commit with git commit -m "...".
Check upstream with git rev-parse --abbrev-ref --symbolic-full-name @{u}.
Use git push when upstream exists, or git push -u origin <branch> when 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 --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.