merge

Installation
SKILL.md

Merge

Take one branch onto one base through its pull request: find or open the PR, wait for its CI, merge it with a merge commit, follow the runs the merge triggers, and delete the head when it is short-lived. The merge is the deliverable; commits, conflict resolution, and workflow reruns stay with the user.

Authorisation

Proceed only when the user has asked for this merge in their own words, naming the base: directly ("merge this branch into main", "merge release main"), or as an explicit instruction to the agent running you ("implement X, then merge it into main"). An agent's or skill's own judgement that work is ready is never authorisation. Without that request, or without a named base, stop and ask.

Arguments

Parsed loosely from the request:

  • Base (required): the branch to merge into.
  • Head (optional): the branch to merge. Defaults to the current branch.

merge release main reads as head release, base main; merge this into main reads as head <current branch>, base main.

Long-lived branch

Installs
1
First Seen
7 days ago