ClawHub

windows-git-ops

v1.0.0

Use this skill when performing Git operations in a Windows PowerShell workspace, especially for branch creation, staging, commit, merge, status inspection, a...

⭐ 0· 37·0 current·0 all-time
by@zhangchaoqing5
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/description (Windows PowerShell Git operations) align with the SKILL.md content. The skill only describes git commands and PowerShell-safe patterns and does not declare or require unrelated binaries, credentials, or config paths.
✓
Instruction Scope
SKILL.md limits actions to inspecting and performing Git operations, emphasizes non-interactive commands, and instructs verification before mutating state. It does not instruct reading unrelated files, accessing secrets, or contacting external endpoints.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk or downloaded during install.
✓
Credentials
No environment variables, credentials, or config paths are requested. The guidance about setting env vars uses normal PowerShell syntax and is conditional to commands that need them.
✓
Persistence & Privilege
always is false and the skill does not request persistent privileges or to modify other skills or system-wide settings. Autonomous invocation is allowed by platform default but not excessive here.
Assessment
This skill is coherent and appears to do only what it says: generate and recommend PowerShell-safe Git commands and workflows. Before enabling or letting an agent run it, remember: (1) the agent will produce commands that could modify your repo—review commands before execution or run them in a safe/test repo; (2) it uses the 'codex/' branch prefix by policy—confirm you want that naming convention; and (3) because it is an instruction-only skill, there are no additional downloads or secret requests, but you should still limit an agent's repository access and prefer explicit, user-confirmed execution for any destructive operations (resets, discards, merges).

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

latestvk97e442r5twk6c0qshdhezc8s184ter1

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments