This page contains 7 additions and 151 deletions.
Need
How Codex reads it
Default options
Plugins for Slack, Linear, GitHub, and Sentry; connectors; MCP servers ; repo CLIs; links; exports; attachments; and pasted logs
Why it's needed
Install the existing integration when there is one. Build or configure a small MCP server, CLI, export, or dashboard link for internal sources Codex cannot read yet.
11name: Automate bug triage# Automate bug triage | Codex use cases
2tagline: Turn daily bug reports into a prioritized list, then automate the sweep.
3summary: Ask Codex to check recent alerts, issues, failed checks, logs, and chat
4 reports, tune the list in one thread, then run that sweep on a schedule.
5skills:
6 - token: github
7 url: https://github.com/openai/plugins/tree/main/plugins/github
8 description: Read issues, pull requests, comments, review threads, and failed
9 checks when GitHub is part of your bug intake.
10 - token: $sentry
11 url: https://github.com/openai/skills/tree/main/skills/.curated/sentry
12 description: Inspect production errors, stack traces, affected releases, and
13 event context when alerts are part of the sweep.
14 - token: slack
15 url: https://github.com/openai/plugins/tree/main/plugins/slack
16 description: Read the channels or threads where teammates report bugs and
17 prepare a draft summary for a team channel.
18 - token: linear
19 url: https://github.com/openai/plugins/tree/main/plugins/linear
20 description: Read bug queues, find existing issues, draft updates, or prepare
21 linked follow-up tickets after the triage pass.
22bestFor:
23 - Teams that track bugs across Sentry alerts, Slack threads, Linear issues,
24 GitHub issues, failing PR checks, support tickets, or logs.
25 - Triage workflows you want to run manually in one Codex thread before
26 scheduling as an automation.
27starterPrompt:
28 title: Run a Bug Triage Sweep
29 body: >-
30 Run a bug triage sweep for [repo/service/team] covering the last [time
31 window].
32 2
3Need
33 4
345 Use these plugins: [@Sentry / @Slack / @Linear / @GitHub / none]How Codex reads it
35 6
7Default options
36 8
379 Input sources:[Plugins](https://developers.openai.com/codex/plugins) for Slack, Linear, GitHub, and Sentry; connectors; [MCP servers](https://developers.openai.com/codex/mcp) ; repo CLIs; links; exports; attachments; and pasted logs
38 10
3911 - Sentry: [project / alert link / none]Why it's needed
40 12
4113 - Slack: [channel / thread links / none]Install the existing integration when there is one. Build or configure a small MCP server, CLI, export, or dashboard link for internal sources Codex cannot read yet.
42 14
43 - Linear: [team / project / view / issue query / none]
44
45 - GitHub: [repo / issue query / PR checks / none]
46
47 - Other: [logs / support tickets / deploy link / dashboard / attached file /
48 none]
49
50
51 Output format:
52
53 First, name any input source you could not access.
54
55 Then return a prioritized list of bugs, sorted from P0 to P3.
56
57 If you find no bugs, say: No qualifying bugs found.
58
59
60 For each bug, include:
61
62 - Priority: P0, P1, P2, or P3
63
64 - Title
65
66 - Evidence (links or short citations)
67
68 - Recommended next action
69
70
71 Rules:
72
73 - Do not post, create, assign, label, close, rerun, or edit anything.
74
75 - Group duplicate reports under one bug.
76
77 - Keep observed evidence separate from guesses.
78relatedLinks:
79 - label: Codex automations
80 url: /codex/app/automations
81 - label: Codex plugins
82 url: /codex/plugins
83 - label: Codex MCP
84 url: /codex/mcp
85 - label: Use Codex in Linear
86 url: /codex/integrations/linear
87techStack:
88 - need: Where bug context gathers
89 goodDefault: Sentry alerts, Slack channels, Linear views, GitHub issues, PR
90 checks, support queues, on-call notes, logs, dashboards, and deploy notes
91 why: Name the exact queues, channels, views, repos, alert links, dashboards, and
92 files Codex should sweep.
93 - need: How Codex reads it
94 goodDefault: "[Plugins](/codex/plugins) for Slack, Linear, GitHub, and Sentry;
95 connectors; [MCP servers](/codex/mcp); repo CLIs; links; exports;
96 attachments; and pasted logs"
97 why: Install the existing integration when there is one. Build or configure a
98 small MCP server, CLI, export, or dashboard link for internal sources
99 Codex cannot read yet.
100
101## How to use
102
103Ask Codex to check the places where bugs already appear: Sentry alerts, Linear issues, GitHub issues, PR checks, deploy logs, support tickets, and Slack threads. Start with one manual sweep, tune the report in-thread, then run it on a schedule.
104
105Use one Codex thread for the whole triage loop:
106
107
108
1091. Run an on-demand sweep and get a draft list.
1102. Review the list and give feedback in that same thread.
1113. Turn that same thread into an automation.
1124. Optional: ask Codex to draft Linear issues, Slack updates, GitHub comments, or handoff notes when you are confident in the report.
113
114
115
116Before you start, install the [plugins](https://developers.openai.com/codex/plugins) Codex needs, such as Sentry, Slack, Linear, or GitHub. In the starter prompt, replace the bracketed plugin list with real `@` plugin chips. Then replace each bracketed source with the exact place to search: a Sentry project or alert URL, Slack channel or thread, Linear team, view, or query, GitHub repo, issue query, or PR check, deploy link, log file, support queue, or dashboard.
117
118## Phase 1: Run the sweep
119
120Start Codex from the repo that owns the bugs when local context helps: tests, repo tooling, build checks, or CI failures. You can also run the sweep from any repo if your bug sources are available through plugins, connectors, MCP servers, links, exports, pasted logs, or attachments.
121
122Run the starter prompt above first. Keep only the plugins and sources that are part of your sweep.
123
124For example, a filled-in prompt can name the plugins and the exact queues, channels, or repos you want in the sweep.
125
126<div class="not-prose mb-12 rounded-xl bg-[url('/images/codex/codex-wallpaper-1.webp')] bg-cover bg-center p-4 md:p-8">
127 </div>
128
129## Phase 2: Make the report useful
130
131Before you automate, make sure the report is useful enough to read every day.
132
133A useful first run has:
134
135- High-signal bugs sorted from P0 to P3.
136- Duplicate reports are grouped under one bug.
137- Each bug has linked evidence or short citations.
138- Guesses are separated from observed facts.
139- Each bug has a short recommended next action.
140
141Tune the report in the same thread before you automate it. You can ask Codex to:
142
143- Check one more source before ranking the list.
144- Drop noisy alerts that the team already knows about.
145- Only return P0 and P1 bugs.
146- Merge Slack reports, Sentry alerts, and GitHub failures when they point to the same bug.
147- Show the single best link for each bug.
148- Add enough evidence that someone else can reproduce or route the issue.
149
150## Phase 3: Automate it
151
152When the on-demand report is useful, stay in the same thread and turn it into an automation. Codex can use what you refined in the thread to write the recurring automation prompt.
153
154**Create the automation**
155
156## Phase 4: Route follow-ups
157
158Once the scheduled report is useful, decide where the work should go next. Codex can draft a Slack update for a team channel, write Linear issues for the bugs you want to track, write GitHub comments for a failing PR, or produce a handoff for whoever is on call.
