GitHub Issue Maintainer

GitHub issue agent for Eve.

What is GitHub Issue Maintainer?

GitHub Issue Maintainer is an Eve agent that Labels GitHub issues, asks for missing repro, and emails a weekly digest. It is for Eve developers building with code. Preview every file on this page, then install with npx shadcn@latest add @evex/github-issue-maintainer. GitHub Issue Maintainer is an eve agent that triages newly opened GitHub issues through a native GitHub App channel.

Labels GitHub issues, asks for missing repro, and emails a weekly digest.

Other package managers

Prefer pnpm, yarn, or bun? Copy the matching install command.

npx shadcn@latest add @evex/github-issue-maintainer

Category: coding
Files: 23 files
Requires: 6 dependencies
Updated: Aug 24, 2026

What's included

23 files1 skill file5 tools

Dependencies:@upstash/ratelimit@^2.0.8@upstash/redis@^1.38.0ai@^7.0.38eve@^0.31.3resend@^6.14.0zod@4.3.6

About GitHub Issue Maintainer

GitHub Issue Maintainer is an eve agent that triages newly opened GitHub issues through a native GitHub App channel. When an issue opens, GitHub delivers the webhook to your deployed eve app at /eve/v1/github, and the agent applies a small label taxonomy, then asks for missing reproduction details when the report is thin.

It is adjacent to Code Reviewer in the same GitHub App and issue-comment world, but it never reviews pull requests and never publishes GitHub PR reviews. Its job stops at issue hygiene: labeling, clarifying incomplete reports, and a weekly open-issue digest email through Resend.

Built-in Upstash-backed rate limiting keeps public deployments safe, with stricter defaults for public repositories than private ones. The weekly digest is a schedule, not a review workflow: it lists open issues and emails maintainers a concise HTML summary.

How it works

A newly opened issue triggers the GitHub channel onIssue hook, or a user mentions @github-issue-maintainer on an issue timeline comment matching GITHUB_APP_SLUG.
The channel rejects pull request conversations and review threads, then checks Upstash rate limits with short-circuiting cooldowns before the repository daily quota.
When allowed, the channel injects issue title, body, existing labels, bug_like, and thin-issue gap hints into the turn context for the zai/glm-5.2 model.
The agent loads the issue-triage skill when needed, then calls triage_issue exactly once with taxonomy labels and an optional repro-request comment for bug reports only, validated by Zod.
The channel claims publication in Redis, creates any missing taxonomy labels, applies labels through the GitHub Issues API, and posts the repro ask as an issue comment when requested. Failed publishes release the claim so retries can proceed.
Separately, the weekly-issue-digest schedule calls list_open_issues, compose_digest_html (HTML-escaped titles), preview_digest_email, and send_digest_email with confirmSend and an ISO-week idempotency key.

Use cases

Auto-label incoming bug and feature reports

Install the GitHub App on team repositories so every new issue gets a bug, feature, docs, question, or chore label without a human sorting the inbox first. Maintainers open the board already grouped by type.

Ask for missing repro on thin reports

Drive-by issues that say it does not work get a short comment asking for reproduction steps, expected versus actual behavior, and environment details, so maintainers are not stuck guessing.

Weekly open-issue digest for solo maintainers

Every Monday the schedule emails a digest of open issues grouped by needs attention, recently updated, and stale, so freelancers and small teams can scan the backlog from their inbox.

Safe triage on public open-source repos

Upstash-backed limits default to 15 triages per public repository per day with per-issue and per-user cooldowns, so drive-by mentions cannot exhaust your model budget.

Requirements

GITHUB_APP_ID: The App ID of the GitHub App you create under GitHub Settings, Developer settings, GitHub Apps. The app needs Metadata read, Issues read/write, and Contents read. Do not grant Pull requests write.
GITHUB_APP_PRIVATE_KEY: The PEM private key generated from the GitHub App settings page. When stored as a single-line variable, replace literal newlines with \n; eve normalizes that form at runtime.
GITHUB_WEBHOOK_SECRET: A long random value set both in the GitHub App webhook configuration and in your deployment. A mismatch produces HTTP 401 responses at /eve/v1/github.
GITHUB_APP_SLUG: The mention users type on GitHub, defaulting to github-issue-maintainer. It must match your GitHub App name so mentions trigger the agent.
GITHUB_APP_INSTALLATION_ID: The installation id for the repository used by the weekly digest list_open_issues tool. Required for scheduled digest API reads.
KV_REST_API_URL: Upstash Redis REST endpoint used by @upstash/ratelimit for cooldowns, daily quotas, and duplicate-publication claims. Provision it via Upstash or the Vercel Redis Marketplace integration.
KV_REST_API_TOKEN: The matching Upstash REST token. Use a read-write token, not the read-only one, because the agent writes cooldown and triage publication keys.
ISSUE_DIGEST_REPO: owner/repo for the weekly open-issue digest. The schedule lists open issues from this repository only.
ISSUE_DIGEST_FROM: Verified Resend sender address used for the weekly digest email.
ISSUE_DIGEST_TO: Comma-separated recipient list for the weekly digest email.
RESEND_API_KEY: Resend API key used by send_digest_email after preview_digest_email confirms the payload.
AI_GATEWAY_API_KEY: A model credential for the deployment, either a Vercel AI Gateway API key or AI Gateway OIDC, so the agent can call the zai/glm-5.2 model.

FAQ

How do I install and trigger it?

Run npx shadcn@latest add @evex/github-issue-maintainer inside an eve app, deploy it over HTTPS, create a GitHub App pointing its webhook at /eve/v1/github, subscribe to Issues and Issue comments, install it on your repositories, then open a new issue or comment @github-issue-maintainer on an issue.

Does it review pull requests?

No. The channel ignores pull request conversations and review threads, and the agent has no PR review publication path. Use @evex/code-reviewer when you need GitHub PR reviews with inline comments.

Which labels does it apply?

Only bug, feature, docs, question, and chore. The taxonomy is documented in the package README and the issue-triage skill. Create those labels in the repository or allow the app to create them on first use.

How does the weekly digest work?

A cron schedule (default Mondays at 09:00 UTC) calls list_open_issues for ISSUE_DIGEST_REPO, composes HTML, previews with preview_digest_email, then sends through Resend with confirmSend and an idempotency key so retries never duplicate the email.

How do the rate limits work?

Defaults are one triage per issue every 15 minutes, one per user per issue every 30 minutes, 50 daily triages per private repository, and 15 per public repository. Tune with ISSUE_MAINTAINER_* variables, or disable with ISSUE_MAINTAINER_RATE_LIMIT_ENABLED=false for local development.

Files this command writes

Core

Skills

Tools

npx shadcn@latest add @evex/github-issue-maintainer

What is GitHub Issue Maintainer?

Other package managers

Prefer pnpm, yarn, or bun? Copy the matching install command.

npx shadcn@latest add @evex/github-issue-maintainer

Auto-label incoming bug and feature reports

Ask for missing repro on thin reports

Drive-by issues that say it does not work get a short comment asking for reproduction steps, expected versus actual behavior, and environment details, so maintainers are not stuck guessing.

Weekly open-issue digest for solo maintainers

Every Monday the schedule emails a digest of open issues grouped by needs attention, recently updated, and stale, so freelancers and small teams can scan the backlog from their inbox.

Safe triage on public open-source repos

Upstash-backed limits default to 15 triages per public repository per day with per-issue and per-user cooldowns, so drive-by mentions cannot exhaust your model budget.

Requirements

GITHUB_APP_ID

The App ID of the GitHub App you create under GitHub Settings, Developer settings, GitHub Apps. The app needs Metadata read, Issues read/write, and Contents read. Do not grant Pull requests write.

GITHUB_APP_PRIVATE_KEY

The PEM private key generated from the GitHub App settings page. When stored as a single-line variable, replace literal newlines with \n; eve normalizes that form at runtime.

GITHUB_WEBHOOK_SECRET

A long random value set both in the GitHub App webhook configuration and in your deployment. A mismatch produces HTTP 401 responses at /eve/v1/github.

GITHUB_APP_SLUG

The mention users type on GitHub, defaulting to github-issue-maintainer. It must match your GitHub App name so mentions trigger the agent.

GITHUB_APP_INSTALLATION_ID

The installation id for the repository used by the weekly digest list_open_issues tool. Required for scheduled digest API reads.

KV_REST_API_URL

Upstash Redis REST endpoint used by @upstash/ratelimit for cooldowns, daily quotas, and duplicate-publication claims. Provision it via Upstash or the Vercel Redis Marketplace integration.

KV_REST_API_TOKEN

The matching Upstash REST token. Use a read-write token, not the read-only one, because the agent writes cooldown and triage publication keys.

ISSUE_DIGEST_REPO

owner/repo for the weekly open-issue digest. The schedule lists open issues from this repository only.

ISSUE_DIGEST_FROM

Verified Resend sender address used for the weekly digest email.

ISSUE_DIGEST_TO

Comma-separated recipient list for the weekly digest email.

RESEND_API_KEY

Resend API key used by send_digest_email after preview_digest_email confirms the payload.

AI_GATEWAY_API_KEY

A model credential for the deployment, either a Vercel AI Gateway API key or AI Gateway OIDC, so the agent can call the zai/glm-5.2 model.

FAQ

How do I install and trigger it?

Does it review pull requests?

No. The channel ignores pull request conversations and review threads, and the agent has no PR review publication path. Use @evex/code-reviewer when you need GitHub PR reviews with inline comments.

GitHub Issue Maintainer

What is GitHub Issue Maintainer?

Other package managers

What's included

About GitHub Issue Maintainer

How it works

Use cases

Auto-label incoming bug and feature reports

Ask for missing repro on thin reports

Weekly open-issue digest for solo maintainers

Safe triage on public open-source repos

Requirements

FAQ

How do I install and trigger it?

Does it review pull requests?

Which labels does it apply?

How does the weekly digest work?

How do the rate limits work?

Files this command writes

Core

.env.example.env.example31 lines

agent.tsagent/agent.ts6 lines

github.tsagent/channels/github.ts415 lines

instructions.mdagent/instructions.md55 lines

github-app.tsagent/lib/github-app.ts127 lines

html.tsagent/lib/html.ts10 lines

issue-config.tsagent/lib/issue-config.ts82 lines

issue-rate-limit.tsagent/lib/issue-rate-limit.ts429 lines

taxonomy.tsagent/lib/taxonomy.ts24 lines

thin-issue.tsagent/lib/thin-issue.ts108 lines

weekly-issue-digest.tsagent/schedules/weekly-issue-digest.ts19 lines

ask-repro-thin-issue.eval.tsevals/ask-repro-thin-issue.eval.ts36 lines

evals.config.tsevals/evals.config.ts6 lines

ignore-pull-request.eval.tsevals/ignore-pull-request.eval.ts42 lines

label-clear-bug.eval.tsevals/label-clear-bug.eval.ts43 lines

no-repro-on-feature.eval.tsevals/no-repro-on-feature.eval.ts32 lines

README.mdagent/README.md179 lines

Skills

SKILL.mdagent/skills/issue-triage/SKILL.md46 lines

Tools

compose_digest_html.tsagent/tools/compose_digest_html.ts55 lines

list_open_issues.tsagent/tools/list_open_issues.ts99 lines

preview_digest_email.tsagent/tools/preview_digest_email.ts34 lines

send_digest_email.tsagent/tools/send_digest_email.ts101 lines

triage_issue.tsagent/tools/triage_issue.ts73 lines

GitHub Issue Maintainer

What is GitHub Issue Maintainer?

Other package managers

What's included

About GitHub Issue Maintainer

How it works

Use cases

Auto-label incoming bug and feature reports

Ask for missing repro on thin reports

Weekly open-issue digest for solo maintainers

Safe triage on public open-source repos

Requirements

FAQ

How do I install and trigger it?

Does it review pull requests?

Which labels does it apply?

How does the weekly digest work?

How do the rate limits work?

Files this command writes

Core

.env.example.env.example31 lines

agent.tsagent/agent.ts6 lines

github.tsagent/channels/github.ts415 lines

instructions.mdagent/instructions.md55 lines

github-app.tsagent/lib/github-app.ts127 lines

html.tsagent/lib/html.ts10 lines

issue-config.tsagent/lib/issue-config.ts82 lines

issue-rate-limit.tsagent/lib/issue-rate-limit.ts429 lines

taxonomy.tsagent/lib/taxonomy.ts24 lines

thin-issue.tsagent/lib/thin-issue.ts108 lines

weekly-issue-digest.tsagent/schedules/weekly-issue-digest.ts19 lines

ask-repro-thin-issue.eval.tsevals/ask-repro-thin-issue.eval.ts36 lines

evals.config.tsevals/evals.config.ts6 lines

ignore-pull-request.eval.tsevals/ignore-pull-request.eval.ts42 lines

label-clear-bug.eval.tsevals/label-clear-bug.eval.ts43 lines