merge-it
Merge It
Overview
Use this skill to finish an implementation branch through GitHub by merging into wherever the next integrate target is — not always main/default. Discover that target from repository instructions, the existing PR's base, branch protection, issue/milestone context, or the user's explicit request (staging, release, trunk, default, etc.). Then create or update the PR, apply actionable review feedback with the autofix workflow, verify checks, merge, confirm the issue is closed, and return the local checkout to the correct base branch.
Skill boundaries (avoid contradictory overlap):
| Intent | Skill |
|---|---|
| Complete the feature PR into its configured next target (PR base), including when that base is staging | merge-it (this skill) |
| Named staging land play — stage branch/environment per policy when the user asks to stage / land on staging | stage-it |
| Promote all the way into production and check on it (smoke, golden signals, dashboards, obs) | ship-it |
Prefer stage-it when the user explicitly asked for the staging land play. Prefer merge-it when they asked to finish/land/merge the current PR lifecycle and the next target happens to be staging (or any other base). Prefer ship-it only for production promote + post-prod verify — not for ordinary feature merges onto default/trunk.
When the issue, active plan, or PR body includes lightweight BDD completion scenarios, use them as the human-readable definition of done. Confirm each scenario has corresponding evidence before merging or closing the issue. Evidence can be automated tests, local validation, CI, focused manual verification, documentation proof, or a justified note that the scenario is out of scope or no longer applies. Do not require Cucumber, .feature files, or a separate BDD framework unless the repository already uses one or the active plan explicitly requires it.