---
name: Finishing A Development Branch
slug: finishing-a-development-branch-6
category: Quality
description: Finishing A Development Branch helps you prepare completed work for merge with cleanup, testing, linting, documentation updates, and a structured pull request. Use it before pushing a branch for review.
github: "https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/finishing-a-development-branch"
language: Rust
stars: 195
forks: 12
install: "npx degit https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-branch"
installs_to: ~/.claude/skills/finishing-a-development-branch
source_path: src-tauri/builtin-skills/finishing-a-development-branch/SKILL.md
collection_size: 13
category_size: 1745
collection_url: "https://dirskills.com/collections/peintune/runjam"
added: 2026-09-06T05:18:57.257Z
last_synced: 2026-09-06T05:18:57.257Z
canonical_url: "https://dirskills.com/skills/finishing-a-development-branch-6"
---

# Finishing A Development Branch

Finishing A Development Branch helps you prepare completed work for merge with cleanup, testing, linting, documentation updates, and a structured pull request. Use it before pushing a branch for review.

**Install:**

```bash
npx degit https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-branch
```

## README

# 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
```