cc-skill:finishing-a-development-branch

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you finish a coding task by checking that tests pass, then showing you four clear options: merge locally, create a pull request, keep the branch for later, or discard the work. It handles whichever option you choose and cleans up after itself.

who it is for

Developers who have finished writing code and need a structured way to integrate it into their project.

when it fires

When you say something like 'I'm done with this feature' or 'merge this back' or 'create a pull request' after completing development work.

say something like

"I've finished the authentication feature, what should I do with this branch?"
"All tests are passing, let's wrap this up"
"I'm ready to merge my changes back to main"

what you might get back

Tests passing. Implementation complete. What would you like to do? 1. Merge back to main locally. 2. Push and create a Pull Request. 3. Keep the branch as-is. 4. Discard this work. Which option?

how to know it worked

You'll see it announce the skill at the start, verify your tests pass, and then present exactly four merge options to choose from.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/finishing-a-development-branch/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

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

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/finishing-a-development-branch/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "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"
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/finishing-a-development-branch/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.