9 new issues waiting for triage
Apply the suggested labels and assignees to these 9 issues?
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.
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.
Reads
You get
The card on the right is a sample. Yours shows your own numbers and updates in place every run.
What lands on your board
Apply the suggested labels and assignees to these 9 issues?
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.
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.
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).
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.
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.
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".
With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.
Pick your agent, where the data comes from and how to schedule it; the commands below follow.
One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.
shellcurl -fsSL https://briefkin.dev/skills/github-new-issues-to-triage/install | shAsk Claude Code:
promptRun the github-new-issues-to-triage skillOr paste the prompt instead of installing:
promptUsing the GitHub CLI for <owner>/<repo>, list open issues created since yesterday with no label and no assignee. For each, suggest a type (bug, feature request, question, docs), labels chosen only from the repository's existing labels, and an assignee from CODEOWNERS if one fits. Search open issues for likely duplicates and mark them. Show the list as a table, then ask me whether to apply the suggestions. Change nothing until I answer.Weekdays at 9:00, from cron on any machine where Claude Code is signed in:
crontab0 9 * * 1-5 claude -p "Run the github-new-issues-to-triage skill"Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.
Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a question for you. How setup works
SKILL.md---
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
The gh CLI signed in as someone with triage access to the repository, or a token in GITHUB_TOKEN with Issues read and write.
https://api.githubcopilot.com/mcp/. Sign in with OAuth or a personal access token; add /readonly to the URL, or use a toolset URL such as https://api.githubcopilot.com/mcp/x/pull_requests/readonly, to expose only read tools. It also runs locally (source).gh CLI. Run gh auth login once, or set GH_TOKEN for scheduled runs. gh pr list --search "review-requested:@me" --json number,title,url,createdAt and gh api repos/{owner}/{repo}/dependabot/alerts cover most reports.GITHUB_TOKEN, limit it to the repositories in the report, and grant Read on Metadata, Contents, Pull requests and Issues, plus Dependabot alerts if you report on them.With every permission on a fine-grained token set to Read, the agent can't push, merge, comment or close anything.
No. The card is a question, and the skill runs gh issue edit or closes a duplicate only after you answer. Pick "Go one by one" and it walks through each issue in the chat and waits for your yes or your change.
From the CODEOWNERS file, matched against the area the issue talks about (a path, a feature name, an error from a known module). When nothing matches it leaves the assignee empty instead of picking someone at random.
No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a asks you, so you can glance at it instead of asking again.
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.
Yes. Switch the data source to "Your browser" and the steps change to the GitHub pages themselves: the agent opens github.com/issues in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.
Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.
Free during the open beta. No card.