Skip to main content

Raise PR

Prepare and send concise pull request handoff messages. Use when the user asks to raise a PR, send a PR for review, tag a reviewer, notify a reviewer in Lark, or format a PR handoff message containing a tagged person, PR link, and summary.

Source: .agents/skills/raise-pr/SKILL.md

Metadata​

  • name: raise-pr

Content​

Raise PR

Required Inputs​

Before sending a PR handoff message, confirm these three fields are known:

  • Tagged person: the reviewer or recipient the user explicitly named.
  • PR link: the pull request URL.
  • Summary: a concise summary of the fix.

If the user does not explicitly provide the tagged person, ask who to send/tag before sending anything. Do not infer the reviewer from commit history, PR ownership, recent chat history, or prior habits unless the user names them in the current request.

Message Format​

Use this structure exactly unless the user asks for another format:

{Tagged person}

{PR Link}

Summary: {Summary of fix}

Keep the summary short by default. If the user asks for a limit, obey it; otherwise use one to three sentences.

Workflow​

  1. Identify the PR URL from the user, local branch, or GitHub CLI when needed.
  2. Identify the tagged person only from explicit user instruction. If missing, ask.
  3. Draft the summary from the actual diff, PR description, or recent verified work. Do not invent verification.
  4. Send via Lark only after the recipient and content are clear.
  5. Report where it was sent and include the message ID or URL if the tool returns one.

Channel Notes​

  • Send only in Lark: use lark-im and resolve each tagged person to the correct open_id before sending.
  • For Pull Request Goes Here, use chat ID oc_e2e74c5a34b7c5b724cfcbb70b24933d.