Finishing Branch
v1.0.1Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - presents structured options for merge, PR, or cleanup...
⭐ 0· 148·0 current·0 all-time
by@axelhu
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 (finishing a development branch: test, merge/PR, cleanup) match the SKILL.md instructions. The steps show exactly the git and test operations you'd expect for this task. The skill is instruction-only and therefore declares no required binaries or env vars; that is reasonable but the doc assumes git, language test runners (npm/pytest/cargo/go), and optionally the GitHub CLI (gh) are available.
Instruction Scope
Instructions stay within scope: they run tests, determine base branch, present four explicit options, and perform the chosen git actions. The skill includes potentially destructive operations (git branch -D, pushing, merging) but requires confirmation for the destructive 'discard' path. The instructions do not ask to read unrelated files, environment variables, or exfiltrate data.
Install Mechanism
No install spec (instruction-only), so nothing is downloaded or written to disk by the skill itself — the lowest-risk install profile.
Credentials
The skill declares no environment variables or credentials, which is coherent for an instruction-only helper. However, several steps (git push, gh pr create) implicitly require repository remote credentials or a configured gh CLI — those are assumed to be provided by the user's environment rather than the skill. This is expected but worth verifying before use.
Persistence & Privilege
The skill is not always-enabled and doesn't request persistent system presence or modify other skills. Autonomous invocation is allowed by default on the platform but is not in itself a red flag here.
Assessment
This skill is an instruction-only helper for finishing feature branches; it will present options and run git and test commands when invoked. Before using it: (1) confirm your agent will run commands in the intended repository and working directory (to avoid accidental branch deletion or merges), (2) ensure the test runner(s) and git/GitHub CLI you need are installed and authenticated in your environment, and (3) treat the 'discard' option as destructive — only confirm after you verify the commit list. If you want stricter safety, require explicit user approval before any destructive git command or run the skill in a disposable/test repo first.Like a lobster shell, security has layers — review code before you run it.
latestvk977hfr332kt2v6nvkhyc8jw6h83n94j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.