Commit Push
v1.1.4commit and push all local changes to remote repo
⭐ 0· 40·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description ('commit and push all local changes') aligns with the SKILL.md which only describes reviewing diffs, composing a Conventional Commit message, staging, committing, and running git push. No unrelated binaries, env vars, or capabilities are requested.
Instruction Scope
Instructions stay within the scope of Git workflows (git status, diff, log, add, commit, push). One behavior to note: the recommended workflow stages all changes (git add -A) and pushes them; while coherent with the purpose, this can accidentally include secrets or unwanted files if the user does not review diffs or .gitignore.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is written to disk by the skill itself.
Credentials
The skill declares no required env vars or credentials. It will implicitly use the user's existing git configuration and credential helpers when pushing, which is expected for this functionality.
Persistence & Privilege
always is false and disable-model-invocation is true (skill will not be autonomously invoked by the model). The skill does not request persistent presence or modify other skills/configuration.
Assessment
This skill appears to do exactly what it claims. Before running: review git diff and git status to ensure no secrets or sensitive files are being committed; consider staging selectively instead of git add -A if you need control; confirm the remote and branch you will push to; be aware the push uses your existing git credentials/credential helpers (SSH keys, credential manager, etc.).Like a lobster shell, security has layers — review code before you run it.
latestvk9752xxt9r001xpe0h8mj8fzy183xe33
License
MIT-0
Free to use, modify, and redistribute. No attribution required.