---
name: github-new-issues-to-triage
description: "Every weekday: new GitHub issues with no label and no assignee, grouped by likely type with suggested labels, and a question on who takes each. Use when the user asks for this, or when it runs on a schedule."
---

# GitHub new issues to triage

Every weekday: new GitHub issues with no label and no assignee, grouped by likely type with suggested labels, and a question on who takes each.

Open source maintainers and product teams on GitHub Issues know the pile: new issues arrive with no label, half are questions, a few are duplicates, and the real bug report sits between them for a week. Triage is quick per issue and tiring in bulk.

Every weekday the agent lists the new issues nobody has labeled or assigned, guesses each one's type, searches for duplicates, and suggests labels from the ones your repository already has and an assignee from CODEOWNERS. You answer once and it applies what you approve.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- The `gh` CLI signed in as someone with triage access to the repository, or a token in `GITHUB_TOKEN` with Issues read and write.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **List untriaged issues** (GitHub): Run `gh issue list --repo <owner>/<repo> --search "is:open no:label no:assignee created:>=2026-10-16" --limit 100 --json number,title,body,author,createdAt,url` with the date of the last run (Friday's on a Monday).
2. **Look for duplicates** (GitHub): For each issue run `gh search issues --repo <owner>/<repo> "<key words from the title>" --state open --limit 5 --json number,title`, and treat a near-identical title or the same error message as a likely duplicate.
3. **Suggest type, labels and assignee** (GitHub): Classify each as bug, feature request, question or docs from the title and body. Take labels only from `gh label list --json name`. Suggest an assignee from `CODEOWNERS` for the area the issue mentions, or leave it empty rather than guess.
4. **Ask, then apply** (GitHub): Post the list as an ask. On a yes, run `gh issue edit <number> --add-label "<labels>" --add-assignee <login>`; for a duplicate, comment with a link to the original and close it with `gh issue close <number> --reason "not planned"`.

## Route B: the browser

### What you need

- Signed in to GitHub with triage access or higher on the repository; read-only accounts can build the list but not apply labels or close issues.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://github.com/issues. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Search the untriaged issues**: Replace the search box contents with `is:issue is:open repo:<owner>/<repo> no:label no:assignee created:>=2026-10-16`, using the date of the last run (Friday's on a Monday).
2. **Read and classify each one**: Open each issue and read the body. Classify it as bug, feature request, question or docs. Pick labels only from the repository's **Labels** page, and an owner from `.github/CODEOWNERS` when the issue names an area it covers.
3. **Look for duplicates**: In the repository's **Issues** tab, search `is:open` plus the key words of the title or the exact error message. A near-identical title or the same error is a likely duplicate; note the original's number.
4. **Apply after the answer**: Report the table and ask whether to apply. On a yes, open each issue, set **Labels** and **Assignees** in the right sidebar; for a duplicate, comment with a link to the original and use **Close as not planned** from the close button's menu.

## The report

- **New issues waiting**: how many, by likely type.
- **The list**: issue, type, suggested labels and assignee.
- **Likely duplicates**, each with the issue it repeats.
- The ask: apply all, skip duplicates, go one by one, or leave them.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "github-new-issues-to-triage/<date of this run, e.g. 2026-10-16>",
  "item_key": "github-new-issues-to-triage",
  "project": "acme-web",
  "source": "GitHub new issues to triage skill",
  "kind": "action",
  "title": "9 new issues waiting for triage",
  "summary": "**9 issues** opened in the last day have no label or assignee: **4 bugs**, **3 feature requests** and **2 questions**. #2318 looks like a duplicate of #2290.",
  "action": {
    "request": "Apply the suggested labels and assignees to these 9 issues?",
    "options": [
      "Apply all",
      "Apply all but the duplicate",
      "Go one by one",
      "Leave them"
    ]
  },
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Issue",
          "Type",
          "Labels",
          "Assignee"
        ],
        "align": [
          "left",
          "left",
          "left",
          "left"
        ],
        "rows": [
          [
            "#2311 Crash when exporting a large CSV",
            "Bug",
            "bug, export",
            "theo"
          ],
          [
            "#2312 Support for Postgres 17",
            "Feature",
            "enhancement",
            "None yet"
          ],
          [
            "#2314 How do I set a custom domain?",
            "Question",
            "question",
            "lena"
          ],
          [
            "#2315 Wrong time zone in the weekly email",
            "Bug",
            "bug, email",
            "marco"
          ],
          [
            "#2316 Dark mode for the dashboard",
            "Feature",
            "enhancement",
            "None yet"
          ],
          [
            "#2317 Docs link returns 404 on the API page",
            "Bug",
            "bug, docs",
            "lena"
          ],
          [
            "#2318 Export crashes with 50k rows",
            "Bug, duplicate of #2290",
            "duplicate",
            ""
          ],
          [
            "#2319 Webhook signing with SHA-512",
            "Feature",
            "enhancement, webhooks",
            "sam"
          ],
          [
            "#2320 Is there a rate limit on the API?",
            "Question",
            "question",
            "lena"
          ]
        ]
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Weekdays at 9:00 (`0 9 * * 1-5`). From cron, with the agent signed in on that machine:

```bash
0 9 * * 1-5 claude -p "Run the github-new-issues-to-triage skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/github-new-issues-to-triage#schedule

Source: https://briefkin.dev/skills/github-new-issues-to-triage
