Skip to Content
Use casesIssue triage

Tag an issue and it gets triaged

Add a label and walk away. A deputy reads the issue, adds area labels, asks the reporter for missing details, and tells you when something needs a human. Your issue queue stays organized.

How it works

  • Trigger. A GitHub event, issues.labeled, narrowed to the label needs-triage.
  • What the run does. It finds open issues with that label, reads each one, adds labels, and comments when details are missing.
  • Who is contacted. The deputy’s owner gets a heads-up with the issue links. The deputy can ask the owner a question first when an issue looks sensitive.
  • What you see. Labels and a comment on the issue, and a heads-up on Home, plus a Slack message when your admin has connected Slack.

Set it up

  1. Ask your admin to connect GitHub events once. They install the GitHub package, install the Marshal GitHub App on your GitHub organization, and connect it on Settings > Webhooks. See Sending Marshal a webhook.
  2. Connect GitHub with the Personal access token method. See Connect GitHub.
  3. Create a manifest with the packages claude-code and github.
  4. Open Deputies, select New deputy, and fill in Name, Description, Manifest and Owner.
  5. In the deputy, select New mission. Paste the prompt below into Prompt, select Dry run, then Activate.
  6. Expand the mission. In the Triggers list, select Event.
  7. Set Source to GitHub and Event to issues.labeled.
  8. Add the condition event.label.name == "needs-triage". The dialog previews it against recent real deliveries.
  9. Select Create.

What you should see: the trigger in the mission’s list with an on badge. Add the label needs-triage to an issue. A new run appears for the deputy.

Example mission prompt

Triage issues in the repository acme/web.

1. List open issues that carry the label needs-triage.
2. For each issue, read the description and the comments.
3. Add the labels that fit: bug, feature, docs, or question, plus one
   area label that matches the part of the code it touches.
4. If key details are missing, such as steps to reproduce or the
   version, comment and ask for them in a friendly way.
5. Remove needs-triage when you are done.
6. If an issue might be a security report, do not comment. Ask me first
   with the choices Handle it myself and Go ahead, and wait for my answer.
7. Send me a heads-up with the issue links and what you did.

Make it yours

  • Keep your label list and routing rules in the deputy’s Context.
  • Create a ticket in your tracker for each real bug. Connect linear-mcp or atlassian-mcp. See Integrations.
  • Trigger on issues.opened to triage every new issue.
Cloud cost reportApproval before merge