Merge It
Merge current work to the next integrate target.
What it is
Section titled “What it is”Merge current work to the next integrate target (main/trunk, release branch, staging, or another repo-defined base) — autofix → CI green → merge → close issue. Not production promote. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Trunk-based development and CI require green automated checks before integrate (DORA). GitHub protected branches enforce required status checks so “merge” means “proven,” not “hope.” Closing linked issues completes the audit trail.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”06-work-ownership, 04-evidence-over-vibes
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”merge-it