commit

v1.0.0

Create a git commit with a contextual message based on current changes, then push the branch.

0· 398·6 current·6 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (create a commit and push) align with the instructions: the SKILL.md explicitly reads git status/diff/log, stages changes, commits once, and pushes to origin. No unrelated binaries, env vars, or installs are requested.
Instruction Scope
Instructions stay within git-related operations (status, diff, branch, log, add, commit, push). However, the required sequence stages all changes and pushes to origin, which will modify the remote repository and could publish sensitive changes if present — this is expected for a commit/push skill but is a notable operational risk to be aware of.
Install Mechanism
Instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during install.
Credentials
No environment variables or credentials are requested by the skill. It will rely on whatever git credentials/configuration already exist in the agent's environment (SSH keys, credential helpers), which is appropriate for a git commit/push operation.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent / elevated platform privileges beyond normal agent execution and running Bash commands.
Assessment
This skill will stage all changes and push the current branch to origin using whatever git credentials are configured in the environment — it can therefore publish accidental or sensitive changes. Only allow it to run in repositories you trust, and consider reviewing git status/diff output yourself before invoking. Ensure your environment has the correct remote and credentials, and that you are comfortable with an automated single-commit workflow (no interactive confirmation). If you want more conservative behavior, modify the workflow to prompt before staging/pushing or to exclude certain paths (e.g., secrets).

Like a lobster shell, security has layers — review code before you run it.

latestvk975czahxfbzkz3y6wtr3g4rf181ttwn

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments