finishing-branch
Complete development work by presenting structured options for merge, PR, or cleanup. Use when implementation is complete, all tests pass, and you need to decide how to integrate work. Triggers on finish branch, complete branch, merge branch, create PR, done with feature, implementation complete.
Why use this skill?
Streamline your development workflow with the finishing-branch skill. Safely merge, create PRs, or clean up your Git branches after tests pass.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/finishing-branchWhat This Skill Does
The finishing-branch skill is a structured workflow assistant designed for developers using OpenClaw to manage the end-of-lifecycle phase of feature branches. It acts as a safety layer that ensures development work is properly verified and integrated. By automating the transition from 'implementation' to 'completion,' it helps maintain repository hygiene and reduces the risk of human error during complex merge processes. The skill handles the critical verification stage by forcing a test suite execution, followed by a deterministic set of integration options: local merging, PR creation, postponement, or cleanup and discard. It is designed to act as a project manager, guiding the user through every technical step required to close out a task, from branch deletion to cleaning up local worktrees.
Installation
You can install the skill by executing the following command in your OpenClaw terminal:
clawhub install openclaw/skills/skills/wpank/finishing-branch
Use Cases
- Post-Feature Completion: When you have finished a ticket and need to integrate it without breaking the main build.
- Automated PR Management: When you prefer to use the CLI to generate professional, templated Pull Requests.
- Repository Maintenance: When you need to quickly discard abandoned experiments or clean up local branch clutter after successful merges.
- Worktree Management: When working with multiple git worktrees and needing to ensure that file system pointers are cleaned up correctly upon task completion.
Example Prompts
- "I've finished the feature work on the user-auth branch, can you help me merge it?"
- "All my tests are passing now, please create a PR for this current branch."
- "This experiment didn't work out as expected, please discard the branch and clean up the worktree."
Tips & Limitations
- Testing is Mandatory: The skill refuses to proceed unless tests pass. Ensure your test environment is configured correctly before invoking.
- Branch Strategy: The skill identifies the base branch by looking for 'main' or 'master'. If your team uses a different naming convention (e.g., 'develop' or 'trunk'), ensure you verify the base branch manually.
- Safety First: When discarding, the skill requests manual confirmation. Double-check your branch name before typing 'discard' to prevent accidental data loss.
- Environment Requirements: Ensure
ghCLI is installed and authenticated if you intend to use the PR creation functionality.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-finishing-branch": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, code-execution
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.