Approve & Squash-Merge PR

Given a single PR number, submit an approving review and then squash-merge it. Optionally, if the user supplies a follow-up, file a tracking issue in the same run. Convenience skill for the code-review process — keep it fast and low-friction, but never faster than the merge gates: this skill is one of the QA gate's enforcement points.

Inputs

• PR number (required) — e.g. 2805.
• Repo (optional) — defaults to the repo of the current working directory. If not in a git repo, ask which owner/repo.
• Follow-up (optional) — see Optional follow-up. Triggered by phrasing like "…and add a follow-up", "with follow-up ", "follow-up: ", or a pasted PR/comment link alongside the merge request.

Steps

0. Load pipeline config. Load .ai/agentic.config.json using the standard snippet from the setup-agent-pipeline skill. If the file is missing, stop and tell the user to run setup-agent-pipeline first. This skill uses:

   LABELS_ENABLED=$(jq -r '.labels.enabled // false' "$CONFIG")
   QA_GATE=$(jq -r '.qaGate // false' "$CONFIG")
   

   All label names below come from the config's label taxonomy.