soleri-finishing-a-development-branchlisted

# Finishing a Development Branch Pre-merge checks, PR creation, merge strategy, and branch cleanup. **Announce at start:** "I'm using the finishing-a-development-branch skill to prepare this branch for merge." ## Vault Context Search for merge patterns and known conflict areas: ``` YOUR_AGENT_core op:search_intelligent params: { query: "merge patterns <branch domain>" } YOUR_AGENT_core op:memory_search params: { query: "merge conflicts" } ``` ## Step 1: Pre-Merge Checklist Run all checks before creating a PR. Stop on any failure. ```bash npm test # all tests pass npx tsc --noEmit # typecheck clean npm run lint # no lint errors (if configured) ``` Verify no uncommitted changes: `git status` should be clean. Commit or stash before proceeding. ## Step 2: Create the Pull Request 1. Push the branch: `git push -u origin <branch>` 2. Create PR with `gh pr create`: - **Title**: under 70 chars, conventional format (`feat:`, `fix:`, `refactor:`) - **Body**: summary (what + why), test plan, breaking changes if any - **Reviewers**: add if the user specifies or the repo has CODEOWNERS - **Labels/milestone**: add if relevant Keep the description focused on _why_ the change exists, not a file-by-file diff recap. ## Step 3: Squash vs Merge Commit | Signal | Strategy | Rationale | | -------------------------------- | ---------------- | --------------------------------- | | Many