New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Finishing A Development Branch

by peintune in peintune/runjam

A skill your agent uses when development work is complete and you need to prepare for merge.

MITAuto-check passedDevelopment

Install Finishing A Development Branch

skills CLI
$ npx skills add peintune/runjam --skill finishing-a-development-branch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install peintune/runjam finishing-a-development-branch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src-tauri/builtin-skills/finishing-a-development-branch .claude/skills/finishing-a-development-branch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
finishing-a-development-branch
GitHub stars
228
Token cost
~226 tokens
SKILL.md length
72 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when development work is complete and you need to prepare for merge.

  • Works in 7 steps: Clean up: Remove debug logs,… → Test: Run full test suite, verify edge… → Lint: Run linter and formatter → …
  • Development work is complete and you need to prepare for merge
  • SKILL.md covers Checklist and PR Description Template
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Finishing A Development Branch is an agent skill from peintune/runjam. Use when development work is complete and you need to prepare for merge. Guides through cleanup, testing, documentation, and creating a well-structured pull request.

Its SKILL.md is about 230 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees and Pull requests. The repository describes itself as: One desktop for all your AI coding Agent — Claude Code, Codex CLI & Gemini CLI. Auto-detect, one-click install, unified chat, file explorer, terminal & editor. Local-first. Built… The licence is MIT.

When your agent uses it

  • Development work is complete and you need to prepare for merge
  • Tasks that involve Git worktrees
  • Tasks that involve Pull requests

Example prompts

  • “/finishing-a-development-branch”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Clean up: Remove debug logs, commented-out code, TODO markers
  2. Test: Run full test suite, verify edge cases
  3. Lint: Run linter and formatter
  4. Document: Update README, changelog, or inline docs if needed
  5. Review diff: Self-review the full diff before pushing
  6. Commit: Use descriptive commit messages (what + why, not how)
  7. Push: Push branch and create PR with clear description

What it can do on your machine

Read from SKILL.md and the folder at commit b186c61. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Finishing A Development Branch loads about 226 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 72 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~226

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from peintune/runjam at commit b186c61, republished under its MIT licence (© peintune). 72 words, ~226 tokens.

Download SKILL.mdSave it as .claude/skills/finishing-a-development-branch/SKILL.md (or your agent's skills folder).
name
finishing-a-development-branch
description
Use when development work is complete and you need to prepare for merge. Guides through cleanup, testing, documentation, and creating a well-structured pull request.

Finishing a Development Branch

Checklist

  1. Clean up: Remove debug logs, commented-out code, TODO markers
  2. Test: Run full test suite, verify edge cases
  3. Lint: Run linter and formatter
  4. Document: Update README, changelog, or inline docs if needed
  5. Review diff: Self-review the full diff before pushing
  6. Commit: Use descriptive commit messages (what + why, not how)
  7. Push: Push branch and create PR with clear description

PR Description Template

## What
Brief description of the change

## Why
Why this change is needed

## How
High-level approach (not implementation details)

## Testing
How to verify the change works

© peintune, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src-tauri/builtin-skills/finishing-a-development-branch of peintune/runjam.

Open the folder on GitHubat commit b186c61

Compare with similar skills

Finishing A Development Branch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Finishing A Development Branch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Finishing A Development Branch this skillpeintune/runjam228—~226Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Cap Feature Building WorkflowCapSoftware/Cap23k—~2.5kAutomated safety check: WarnCustom licence
Om Auto Fix Issuego-musicfox/go-musicfox2.6k1 repos~5kAutomated safety check: NotesGPL-3.0
Codewhale Landing Workflowcodewhale-hq/Codewhale41k—~1.6kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

  • Om Auto Fix Issue

    go-musicfox/go-musicfox

    Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…

    2.6k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check: notes

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Clean Complete Branches

    jtenniswood/espcontrol

    Clean up completed Git branches and worktrees for this repository both locally and on GitHub.

    1.1k GitHub stars~820 tokensUpdated today
    DevelopmentAuto-check passed

More from peintune/runjam

  • Mermaid

    peintune/runjam

    Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid.

    228 GitHub starsUsed in 1 repo~729 tokens
    Auto-check passed

  • Ppt Generation

    peintune/runjam

    A skill your agent uses when the user requests to generate, create, or make presentations (PPT/PPTX).

    228 GitHub stars~7.1k tokensUpdated 5 days ago
    Auto-check passed

  • Runjam Defaults

    peintune/runjam

    Default constraints for every RunJam session. An agent skill from peintune/runjam.

    228 GitHub stars~2.7k tokensUpdated 5 days ago
    Auto-check passed

  • Code Review

    peintune/runjam

    A skill your agent uses when reviewing code for bugs, security issues, performance problems, or adherence to best practices.

    228 GitHub stars~244 tokensUpdated 5 days ago
    Auto-check passed

  • Test Driven Development

    peintune/runjam

    A skill your agent uses when implementing any feature or bugfix, before writing implementation code.

    228 GitHub stars~234 tokensUpdated 5 days ago
    Auto-check passed

  • Writing Plans

    peintune/runjam

    A skill your agent uses for complex multi-step tasks. An agent skill from peintune/runjam.

    228 GitHub stars~213 tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Finishing A Development Branch

What does Finishing A Development Branch do?

A skill your agent uses when development work is complete and you need to prepare for merge. Finishing A Development Branch is an agent skill from peintune/runjam. Use when development work is complete and you need to prepare for merge.

When should I use Finishing A Development Branch?

Finishing A Development Branch fits situations like: development work is complete and you need to prepare for merge; tasks that involve Git worktrees; tasks that involve Pull requests.

How do I install Finishing A Development Branch in Claude Code?

Run `npx skills add peintune/runjam --skill finishing-a-development-branch -a claude-code`. Or copy the skill folder (src-tauri/builtin-skills/finishing-a-development-branch in peintune/runjam) into .claude/skills/finishing-a-development-branch in your project. Claude Code loads it when a task matches its description.

How do I install Finishing A Development Branch in Codex?

Run `npx skills add peintune/runjam --skill finishing-a-development-branch -a codex`. Or copy the skill folder (src-tauri/builtin-skills/finishing-a-development-branch in peintune/runjam) into .agents/skills/finishing-a-development-branch in your project. Codex loads it when a task matches its description.

Can I use Finishing A Development Branch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add peintune/runjam --skill finishing-a-development-branch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finishing-a-development-branch, .gemini/skills/finishing-a-development-branch, .github/skills/finishing-a-development-branch and .opencode/skills/finishing-a-development-branch in your project.

What does Finishing A Development Branch need to run?

SKILL.md names no scripts, command-line tools or credentials: Finishing A Development Branch is instructions for the agent only.

Does Finishing A Development Branch access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Finishing A Development Branch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Finishing A Development Branch use?

Finishing A Development Branch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Finishing A Development Branch use?

About 226 tokens (SKILL.md is roughly 904 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Finishing A Development Branch?

Skills that share tags, products or a category with Finishing A Development Branch: Finishing a Development Branch (obra/superpowers, 297k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Cap Feature Building Workflow (CapSoftware/Cap, 23k stars) and Om Auto Fix Issue (go-musicfox/go-musicfox, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Finishing A Development Branch?

peintune (a GitHub user) maintains it in peintune/runjam, which has 228 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: peintune/runjam on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.