Label and sort new GitHub issues
Labels, a priority and a possible duplicate for each new issue, applied after you approve them.
- On an event: When a new issue is opened
- Asks you first
What it does
The task
Read the issues opened in the repository repo since the last run that have no labels. For each one, choose labels from the repository's label list and a priority with these rules: rules. Search the open and closed issues for a duplicate. When a bug report has no version or no steps to reproduce, draft a short comment that asks for them. Ask me before you add labels, post comments or close duplicates.
- It works in GitHub, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- A routine checks every 15 minutes and acts on what is new: when a new issue is opened.
- It stops for your approval before it sends, posts, pays, books or changes a record.
What you give it
| Blank | What to give | Example |
|---|---|---|
| repo | The GitHub repository | brightleaf/sdk |
| rules | How you set priorities, in plain words | P1: data loss, crash or security. P2: bug with a workaround. P3: requests and questions |
What you get back
An example run with the example values above. Your run uses your own data.
3 new issues in brightleaf/sdk
#441 "Upload fails for files over 100 MB": bug, upload, P1
Possible duplicate of #402, closed in v2.3. The bug may be back.
#442 "Add Deno support": enhancement, P3
#443 "It does not work": needs-info, P3
Draft comment: "Thanks for the report. Which version do you use, and what are the steps that show the problem?"
Waiting for your approval on 3 issues.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 2 blanks
Type repo and rules. Tab moves to the next blank.
- 03
Run it, then repeat it
Run sends it once. To run it when a new issue is opened, make a routine on cuiar.com/routines or with the CLI below.
As a routine, from the terminal
cuiar routines create "Label and sort new GitHub issues" --schedule "*/15 * * * *" --time-zone Europe/Berlin \
"Read the issues opened in the repository brightleaf/sdk since the last run that have no labels. For each one, choose labels from the repository's label list and a priority with these rules: P1: data loss, crash or security. P2: bug with a workaround. P3: requests and questions. Search the open and closed issues for a duplicate. When a bug report has no version or no steps to reproduce, draft a short comment that asks for them. Ask me before you add labels, post comments or close duplicates."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool create_routine to run my "Label and sort new GitHub issues" template with repo = brightleaf/sdk; rules = P1: data loss, crash or security. P2: bug with a workaround. P3: requests and questions.Setup for other agents: AI agents.
The tool call
{
"name": "create_routine",
"arguments": {
"name": "Label and sort new GitHub issues",
"task": "Read the issues opened in the repository brightleaf/sdk since the last run that have no labels. For each one, choose labels from the repository's label list and a priority with these rules: P1: data loss, crash or security. P2: bug with a workaround. P3: requests and questions. Search the open and closed issues for a duplicate. When a bug report has no version or no steps to reproduce, draft a short comment that asks for them. Ask me before you add labels, post comments or close duplicates.",
"schedule": "*/15 * * * *",
"time_zone": "Europe/Berlin"
}
}Related templates
All engineering templatesEngineering
Find why a deploy failed
The error from the build log, the change that caused it and a suggested fix, sent when a deploy fails.
On an event: When a deploy fails in Vercel- Vercel
- GitHub
EngineeringAsks first
Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
You start it: When you start it- GitHub
Engineering
Read the changelogs before you upgrade dependencies
Breaking changes, security fixes and upgrade steps for each outdated package, from its release notes.
You start it: When you start it- GitHub
- npm
- PyPI
Engineering
Sort the security alerts in your repositories
Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.
On a schedule: Every Monday at 9:30- GitHub
Engineering
List pull requests that wait for review
Open PRs across your repos with age, reviewers and CI status, the oldest first.
On a schedule: Every weekday at 10:00- GitHub
Engineering
Find flaky tests in your CI runs
Tests that fail and then pass on the same commit, with the count and the error, from your recent runs.
You start it: When you start it- GitHub
- Google Sheets