community-automations/linear-bug-classifier

DevOps & Code

PublicClaude subagent

Linear Bug Classifier

New bugs pile up in one inbox and sit there until someone manually reads, labels, and assigns each one. That manual triage is where hours quietly go.

sonnet2 daysLinearOpenAIGitHubSlack
ClaudeClaude
ROI for
README.md

Why this subagent

New bugs pile up in one inbox and sit there until someone manually reads, labels, and assigns each one. That manual triage is where hours quietly go.

This classifier reads every incoming Linear bug, infers the affected area and severity, and routes it to the right team with a short note. The right people see the right bugs without a triage meeting, and nothing waits unlabeled overnight.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

Read a new Linear bug report and return the affected component, a severity level, the owning team, and a one-sentence triage note explaining the routing.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.