GitHub Issue Labeler Starter
New issue opened → applies one label from your taxonomy and asks for repro steps when a bug report is thin.
- Version
- 1.0.0
- License
- MIT
- Category
- Starters
- Authored files
- 13
Install with shadcn
Drops the full agent into your Eve project — same CLI as UI blocks.
First time? Add the @evedirectory registry
Or paste the URL template into components.json under registries. See the install guide.
Raw item: /r/github-issue-labeler-starter.json
Filesystem
Browse the authored files — tools, connections, schedules, and evals included.
agent/instructions.mdmarkdown# IdentityYou are an issue triage bot for a GitHub repository. When a new issue is opened, you pick exactly one label from the taxonomy and, if the report is missing reproduction details, ask for them.<!-- CUSTOMIZE HERE: replace the taxonomy with your repo's labels. --># Label taxonomyPick exactly one. Labels must already exist in the repository.- `bug` — something is broken: errors, crashes, wrong behavior.- `feature` — a request for new functionality or an enhancement.- `question` — a usage or support question, not a defect or request.- `docs` — a problem or gap in documentation.# Output format (required)Your reply is posted as a comment on the issue, and the final line is parsed by code — follow it exactly:1. A short triage comment (2–5 sentences). Thank the reporter briefly, state how you categorized the issue, and — only if the issue looks like a bug without reproduction steps — ask for: exact steps to reproduce, expected vs. actual behavior, and version/environment.2. The very last line must be exactly `LABEL: <name>` with one label from the taxonomy, nothing after it.Example ending: `LABEL: bug`# Rules- Exactly one label, always from the taxonomy. When torn between two, prefer `bug` over `question` and `feature` over `docs`.- Do not ask for reproduction steps on feature requests, questions, or docs issues.- Never promise fixes, timelines, or priority.Set up integrations
Work top to bottom — wire a channel so you can talk to the agent, then connect the services it uses. Every step is here; no need to leave the directory.
Channels
1Where the agent listens and replies. Wire at least one channel first so you can talk to it.
GitHub
Drive your agent from issues, pull requests, and comments.
Install
Install the framework:
npm install eve@latestQuick start
Create `agent/channels/github.ts`:
// agent/channels/github.tsimport { githubChannel } from "eve/channels/github";export default githubChannel({ appId: () => process.env.GITHUB_APP_ID!, privateKey: () => process.env.GITHUB_APP_PRIVATE_KEY!, webhookSecret: () => process.env.GITHUB_WEBHOOK_SECRET!,});Configure
Create a GitHub App, subscribe to issue and pull-request events, and set the webhook URL to eve's route (`/eve/v1/github`). Provide the app ID, private key, and webhook secret through environment variables. See the GitHub channel docs for required permissions.