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…
Skill by alexsandrocruz
Chalk Labs
Need help deploying finishing-a-development-branch?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/alexsandrocruz-finishing-a-development-branch
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
finishing-a-development-branch- Description
- 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
- License
- MIT
- Instructions
- 197 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Finishing a Development Branch ## Overview Guide completion of development work by presenting clear options and handling chosen workflow. **Core principle:** Verify tests → Present options → Execute choice → Clean up. **Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work." ## The Process ### Step 1: Verify Tests **Before presenting options, verify tests pass:** ```bash # Run project's test suite dotnet test / npm test / cargo test / pytest / go test ./... ``` **If tests fail:** ``` Tests failing (<N> failures). Must fix before completing: [Show failures] Cannot proceed with merge/PR until tests pass. ``` Stop. Don't proceed to Step 2. **If tests pass:** Continue to Step 2. ### Step 2: Determine Base Branch ```bash # Try common base branches git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null ``` Or ask: "This branch split from main - is that correct?" ### Step 3: Present Options Present exactly these 4 options: ``` Implementation complete. What would you like to do? 1. Merge back to <base-branch> locally 2. Push and create a Pull Request 3. Keep the branch as-is (I'll handle it later) 4. Discard this work Which option? ``` **Don't add explanation** - keep options concise. ### Step 4: Execute Choice #### Option 1: Merge Locally ```bash # Switch to base branch git checkout <base-branch> # Pull latest git pull # Merge feature branch git merge <feature-branch> # Verify tests on merged result <test command> # If tests pass git branch -d <feature-branch> ``` Then: Cleanup worktree (Step 5) #### Option 2: Push and Create PR ```bash # Push branch git push -u origin <feature-branch> # Create PR gh pr create --title "<title>" --body "$(cat <<'EOF' ## Summary <2-3 bullets of what changed> ## Test Plan - [ ] <verification steps> EOF )" ``` Then: Cleanup worktree (Step 5) #### Option 3: Keep As-Is Report: "Keeping branch <name>. Worktree preserved at <path>." **Don't cleanup worktree.** #### Option 4: Discard **Confirm first:** ``` This will permanently delete: - Branch <name> - All commits: <commit-list> - Worktree at <path> Type 'discard' to confirm. ```
From alexsandrocruz/ZenPowers, MIT.
More from alexsandrocruz/ZenPowers
- 0.429score
executing-plans
alexsandrocruz
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
writing-plans
alexsandrocruz
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
brainstorming
alexsandrocruz
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
dispatching-parallel-agents
alexsandrocruz
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
systematic-debugging
alexsandrocruz
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
receiving-code-review
alexsandrocruz
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
requesting-code-review
alexsandrocruz
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
using-zenpowers
alexsandrocruz
Use when starting any conversation - establishes mandatory workflows for finding and using ZenPowers skills, including using Read tool before announcing…
SkillFFreshness: F★ 7Claude Code +9 - 0.399score
testing-anti-patterns
alexsandrocruz
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production…
SkillFFreshness: F★ 7Claude Code +9 - 0.399score
testing-skills-with-subagents
alexsandrocruz
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to…
SkillFFreshness: F★ 7Claude Code +9 - 0.395score
writing-skills
alexsandrocruz
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with…
SkillFFreshness: F★ 7Claude Code +9
Signals
- Stars
- 7
- Forks
- 1
- Open issues
- 0
- Last commit (this folder)
- Oct 23, 2025 (1 year ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/alexsandrocruz/ZenPowers
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from alexsandrocruz
- 0.429score
executing-plans
alexsandrocruz
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
writing-plans
alexsandrocruz
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
brainstorming
alexsandrocruz
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured…
SkillFFreshness: F★ 7Claude Code +9 - 0.429score
dispatching-parallel-agents
alexsandrocruz
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
systematic-debugging
alexsandrocruz
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern…
SkillFFreshness: F★ 7Claude Code +9 - 0.404score
receiving-code-review
alexsandrocruz
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires…
SkillFFreshness: F★ 7Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get finishing-a-development-branch running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
finishing-a-development-branch skill. Agent Mart. https://agentmart.dev/skills/alexsandrocruz-finishing-a-development-branch (last updated 2026-10-24)