Engineering Outer Loop Bot
A Grok teammate that triages your repos at 9:00 and drafts release notes. It never merges.
GetKits 제작
차이를 직접 확인하세요
Tuesday 9:00 triage with a red main
사용 전
Weekday routine, Tue 2026-09-29 9:00 AM ET, northwind/platform and northwind/web. 14 open PRs, platform CI on main failing since 07:42, 3 new unlabeled issues, review SLA 24 hours.
사용 후
Main: platform RED since 07:42 (CI #5120), first bad commit a71e0d2 (#1944). web green. Top 3 today: 1. Fix main: #1944 uses OrdersResponse.nextPage, renamed by #1941 four minutes earlier. Dana to fix forward, or a human reverts #1944 2. Review platform#1931 (Marco, 28 h over SLA) 3. Review web#879 security bump once CI passes Approval needed: post this to #eng-outer-loop? Reply post, or edit.
Web release notes with a revert and a flagged feature
사용 전
Thu 2026-10-08, 11:40 AM ET. Leo, release owner, to the Bot: /release-notes-draft since v3.14.0 for northwind/web Merged into main since v3.14.0 (Thu 2026-10-01): #877 feat(orders): saved filters on the orders page #879 chore(deps): bump next from 14.2.10 to 14.2.15 (body: fixes a published advisory) #887 fix(settings): persist dark mode on refresh #889 fix(orders): align Export button in Safari #890 feat(orders): bulk select on the orders table #892 Revert "feat(orders): bulk select on the orders table" #893 feat(checkout): one-click reorder (body: behind REORDER_ENABLED, default off) #895 chore(deps): bump date-fns from 3.6.0 to 3.6.1 #896 chore(deps): bump @tanstack/react-table from 8.20.1 to 8.20.5 #898 fix(orders): add the missing saved_filters migration (body: #877 merged without it) #900 fix (body: "handle empty state") #901 test: e2e for saved filters
사용 후
RELEASE NOTES Version: v3.15.0 suggested (new features, no breaking changes). Range: v3.14.0...main, 12 PRs, 2026-10-01 to 2026-10-08 Breaking changes None New - Save a set of filters on the Orders page and apply it again in one click. (#877) Fixed - Dark mode stays on after you refresh the page. (#887) - The Export button on the Orders page lines up correctly in Safari. (#889) Security - Updated the web framework to address a published advisory. (#879) <details><summary>Internal (6)</summary>Bulk select added and reverted within this release (#890, #892), saved_filters migration that ships with #877 (#898), date-fns 3.6.1 (#895), @tanstack/react-table 8.20.5 (#896), saved filters e2e tests (#901)</details> Needs confirmation - #893 one-click reorder: behind REORDER_ENABLED, default off. Will it be on in production for this release? If not, it stays out of the notes. - #900 "fix": the body only says "handle empty state". Which screen, and what did users see before? Check: 12 PRs in, 12 accounted for (1 new, 2 fixed, 1 security, 6 internal, 2 to confirm) Slack version: northwind/web v3.15.0 (suggested), Thu 2026-10-08 Breaking changes: none - New: save filters on the Orders page and reapply them in one click - Fixed: dark mode survives a refresh; the Export button lines up in Safari - Security: web framework updated for a published advisory Waiting on authors: #893 (is the reorder flag on?), #900 (what changed for users?) Full notes: the GitHub release, once Leo publishes it Approval needed: post the Slack version to #eng-outer-loop?
Red main at 07:42 to a verdict and a Slack draft
사용 전
GitHub notification: workflow CI failed on main in northwind/platform. Run #5120, commit a71e0d2 "feat(api): add cursor pagination to /v2/orders (#1944)". Failing step Typecheck: src/sdk/orders.ts(88,17): error TS2339: Property 'nextPage' does not exist on type 'OrdersResponse'. ##[error]Process completed with exit code 2. Previous run #5119 at 3be91f0 was green. 3be91f0 is "refactor(api): rename nextPage to nextCursor in OrdersResponse (#1941)", merged 4 minutes before #1944. Both PRs were green on their own branches.
사용 후
CI TRIAGE Run: CI / Typecheck, run #5120 on main at a71e0d2 Verdict: REAL (confidence high) Signature: REAL-COMPILE Evidence: Typecheck | src/sdk/orders.ts(88,17): error TS2339: Property 'nextPage' does not exist on type 'OrdersResponse'. Likely cause: Merge skew. #1941 renamed nextPage to nextCursor in OrdersResponse; #1944 merged 4 minutes later and still uses nextPage. Each PR was green on its own branch. A merge queue, or requiring branches to be up to date, would have caught it. First bad commit: a71e0d2 (#1944, Dana). Last green: run #5119 at 3be91f0 (#1941). Smallest next step: Dana changes nextPage to nextCursor at src/sdk/orders.ts:88 in a one-line fix PR. If it is not merged by 10:00 AM, a human reverts #1944. Owner: Dana (author of #1944) Do not: Do not rerun. The failure is deterministic. Approval needed: post to #eng-outer-loop? Slack draft: Main is red on northwind/platform since 07:42 (CI #5120). REAL: #1944 still uses OrdersResponse.nextPage, which #1941 renamed to nextCursor 4 minutes earlier. @Dana can you push the one-line fix? If main is still red at 10:00, revert #1944. Run: github.com/northwind/platform/actions/runs/5120
Four new issues to Linear, one duplicate caught
사용 전
Issues to triage in northwind/platform today: #1957 "Webhook signature mismatch after key rotation": Lumen says every webhook fails verification since they rotated their secret this morning. #1958 "invoices slow": no other text. #1959 "Signature invalid on webhooks": Fernway, same symptom, started 08:10. #1960 "Support PATCH on /v2/customers". Open in Linear PLAT: PLAT-311 "Sender keeps using the old webhook secret for 15 minutes after rotation".
사용 후
ISSUE TRIAGE 1. Issue: platform#1957 Webhook signature mismatch after key rotation (Lumen) Type: bug Priority: High. Webhook delivery broken for a customer with no workaround. Raise to Urgent if more customers report it. Team: PLAT Labels: bug, webhooks Duplicate of: none. Likely cause tracked in PLAT-311 Missing: rotation time and one failing delivery id Proposed action: create a PLAT issue, High, linked to #1957, #1959 and PLAT-311 2. Issue: platform#1959 Signature invalid on webhooks (Fernway) Type: bug Priority: High (same as #1957) Team: PLAT Labels: bug, webhooks Duplicate of: platform#1957 Missing: none Proposed action: comment with a link to #1957, then close as duplicate 3. Issue: platform#1958 invoices slow Type: bug Priority: [confirm] until details arrive Team: PLAT Labels: bug Duplicate of: none found Missing: page or endpoint, account, how slow, since when Proposed action: ask the reporter: "Which page or API call is slow, for which account, and since when? A request id or timestamp helps us find it." 4. Issue: platform#1960 Support PATCH on /v2/customers Type: feature Priority: No priority (feature request, for product review) Team: PLAT Labels: api Duplicate of: none found Missing: the use case behind it Proposed action: create a PLAT issue with No priority for product review Approval needed: create 2 Linear issues (1 and 4), comment on and close #1959, post the question on #1958? Reply approve, approve 1 and 4, or edit.
구성
- engineering-outer-loop-bot-setup.md
Kit 소개
Outer Loop is a Grok Bot that owns the work around your team's code. Every weekday at 9:00 it tells you whether main is green, which PRs are waiting on review and for how long, what is blocked or stale, and which new issues need a team and a priority. When the default branch goes red, it classifies the failure as real, flaky or infra with the log lines that prove it. Every release day it drafts the release notes. It reads GitHub, Linear and Slack freely and writes nothing without your approval. Setup takes about 15 minutes.
What you get
- A ready Bot profile: name, label and a description that sets durable approval boundaries (never merges, pushes, reverts or deploys; posts and comments only after you approve the exact draft).
- Five saved skills, each with inputs, steps, validation and approval rules:
repo-triage: main health, review queue against your SLA, blocked and stale PRs, unlabeled issues, dependency PRs, and the top 3 actions for today.ci-failure-triage: first-error search, a signature list for runner, registry, cache and compile failures, verdict rules, first bad commit and merge skew detection.release-notes-draft: conventional commits and labels to sections, breaking changes first, a count check so no PR goes missing.issue-triage-to-linear: duplicate search, a priority rubric mapped to Linear priorities, team routing, and the one question to ask the reporter.hygiene-sweep: stale PRs, dependency PRs by risk, and flaky tests that meet the quarantine rule.
- Three routines: weekday 9:00 repo triage (with the hygiene sweep on Mondays), a weekly release notes draft, and a narrow event trigger for failed required workflows on the default branch only.
- A setup file with a fill-in table, the paste-in setup message, plugin steps for GitHub, Linear and Slack, a five-check test run and a troubleshooting list.
Who it is for
- Tech leads and engineering managers of teams of 3 to 30 engineers who start each day piecing together GitHub, CI and Linear.
- Teams where reviews wait days, red main goes unnoticed for an hour, or release notes get written at midnight.
- Anyone who wants automation around the code without giving a bot merge rights.
What it will not do
- Merge, approve, push, revert, deploy or change repo settings. It recommends and names who should act.
- Post to Slack, comment on GitHub, rerun workflows or create Linear issues before you approve the exact draft.
- Write or fix product code. Pair it with the Engineering Outer Loop Skill for that side of the work.
- Guess. Unreadable sources are reported at the top of the result, and unknown facts are marked
[confirm]. - Watch every message. The event trigger fires only for failed required workflows on your default branch.
리뷰
아직 리뷰가 없어요.
엔지니어링 Kit 더 보기
Engineering Outer Loop Kit
Run your team's outer loop: daily triage, CI verdicts, release notes and postmortems.
Engineering Outer Loop Dot
Your ChatGPT dot keeps PRs, CI and Linear tidy and brings you only the decisions.
Engineering Outer Loop Skill
Turn diffs, red CI logs and merged PRs into review-ready write-ups with the risk named.