這套分類器會閱讀每一則進來的 Linear bug,推斷受影響的範圍與嚴重程度,再附上一段簡短說明,把它路由給對的團隊。對的人會看到對的 bug,不必再開分流會議,也不會有任何東西掛著沒標標籤過夜。
運作方式
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.
根據文字內容與連結的程式碼路徑,推斷受影響的區域,例如計費、驗證或行動端。
pending
根據描述的衝擊程度設定嚴重性等級,並將該議題指派給負責該區域的團隊。
pending
新增簡短的初篩評論,並在負責團隊的 Slack 頻道發布預警通知。
pending
輸出範例
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.