finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Why use this skill?
Learn to use the OpenClaw finishing-a-development-branch skill to automate test verification, local merges, pull request creation, and repository cleanup.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/zlc000190/finishing-a-development-branchWhat This Skill Does
The finishing-a-development-branch skill serves as an automated project management assistant for OpenClaw agents. It streamlines the lifecycle of a development feature by ensuring code quality through mandatory test verification, followed by a structured workflow for integration. When an agent is tasked with finalizing a feature or bug fix, this skill orchestrates the necessary Git operations—whether that means performing a local merge, facilitating a pull request (PR) via the GitHub CLI, or safely disposing of experimental branches that are no longer needed. By enforcing a test-first completion policy, it prevents broken code from ever reaching a base branch, significantly improving team velocity and repository integrity.
Installation
To install this skill, use the following command within your terminal or OpenClaw interface:
clawhub install openclaw/skills/skills/zlc000190/finishing-a-development-branch
Use Cases
- Feature Completion: After implementing a new requirement, use this to verify all unit tests pass before merging the feature back into the main codebase.
- Automated Pull Requests: Use this to push a branch and automatically generate a structured PR template with a summary of changes and a test plan.
- Experimental Cleanup: Quickly discard local experimental branches and clean up associated git worktrees, ensuring your local environment remains uncluttered.
- CI/CD Workflow Integration: Act as an agentic gatekeeper that enforces local testing standards before any manual or automated push.
Example Prompts
- "I think I'm finished with the authentication feature. Can you use the finishing-a-development-branch skill to wrap this up?"
- "Everything is implemented in this branch. Please run the finishing-a-development-branch skill and prepare a pull request for me."
- "This experiment didn't work out. Run the finishing-a-development-branch skill to discard these changes and clean up the worktree."
Tips & Limitations
- Test Pre-requisite: The skill will halt execution if tests fail. Ensure your project has a working test suite command (e.g.,
npm testorpytest) defined in the environment. - Permission Requirements: Ensure your agent has necessary Git and GitHub CLI (
gh) permissions configured in its environment, as this skill performs direct modifications to the repository. - Confirmation: When choosing to discard work, the skill requires a manual confirmation word ('discard') to prevent accidental data loss.
- Worktree Awareness: The skill is specifically designed to handle Git worktrees, cleaning up temporary directory structures automatically to keep your filesystem organized.
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-zlc000190-finishing-a-development-branch": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution
Related Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.