Finalize Merge Branch
## Finalize & Merge Branch
Prioritize clear, maintainable, and efficient code and organization, delivering robust, fully featured, and best-practice solutions without unnecessary complexity. Solutions should be simple, yet powerful and comprehensive.
1. Before starting, check for any remaining review subtasks in your built-in TODO tool. Confirm that all have been completed before proceeding.
2. Confirm all TODO files (`TODO.md`, and any project or module-specific TODO files) and all project documentation are updated to fully reflect all changes and work completed in the branch.
3. Ensure all automated checks, reviews, tests, and linters have passed.
4. Summarize any remaining open questions or future improvements in a final branch comment, issue note, or in project documentation for visibility to the next reviewer, developer, or future maintainer.
5. Merge the branch into the `main` branch via the approved workflow.
6. After merging:
- Checkout `main` locally.
- Run: `git pull`, `git fetch`, `git prune`.
- Clean up merged feature branches both locally and remotely.
7. Communicate the successful merge and summarize changes to relevant team members if needed, either in a final branch comment, issue, or in team channels.
$ARGUMENTSwhen to use it
Community prompt sourced from the open-source GitHub repo BjornMelin/prompt-atlas (MIT). A "Finalize Merge Branch" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
BjornMelin/prompt-atlas · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar