finishing-a-development-branch

Solid

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.

AI & Automation 231 stars 12 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
79
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
34
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
peintune
Repository
peintune/runjam
Created
1 months ago
Last Updated
6 days ago
Language
Rust
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category