開発アウターループ Bot
9:00 にリポジトリをトリアージし、リリースノートを下書きする Grok のチームメイト。マージは決してしません。
出品者：GetKits
その違いをご覧ください
main が赤い火曜 9:00 のトリアージ
ビフォー
平日ルーティン、2026年9月29日(火) 9:00 ET、northwind/platform と northwind/web。オープンな PR 14件、platform の main の CI が 07:42 から失敗中、ラベルなしの新規 Issue 3件、レビュー SLA は24時間。
アフター
main：platform は 07:42 から赤（CI #5120）、最初の問題コミットは a71e0d2（#1944）。web は緑。 今日の上位3件： 1. main の修正：#1944 が OrdersResponse.nextPage を使っていますが、4分前の #1941 でリネーム済み。Dana が前方修正するか、人間が #1944 をリバート 2. platform#1931 のレビュー（Marco、SLA を28時間超過） 3. CI が通り次第 web#879 のセキュリティ更新をレビュー 承認が必要：これを #eng-outer-loop に投稿しますか？「投稿」または「編集」で返信してください。
Tuesday 9:00 repo triage
ビフォー
Routine weekday-repo-triage fires Tue 2026-09-29, 9:00 AM America/New_York. GitHub right now: - northwind/platform: CI failing on main since 07:42 (run #5120); last green run #5119 at 07:20 - 14 open PRs across northwind/platform and northwind/web, 3 Dependabot PRs, one linking a security advisory - 3 issues opened since Monday 9:00, none labeled - platform#1938 has had changes requested since Friday, no new commits - web#842 is a draft with no activity for 19 days Linear teams PLAT and WEB reachable. Review SLA 24 hours.
アフター
REPO TRIAGE Tue 2026-09-29 9:00 AM ET northwind/platform, northwind/web Main: platform RED since 07:42 (CI #5120). First bad commit a71e0d2 (#1944). web green. Needs review (oldest first, SLA 24 h): - platform#1931 fix(billing): round line items before tax. Priya, waiting 52 h, S, reviewer Marco. Over SLA - web#877 feat: saved filters on orders page. Jonas, waiting 26 h, M, no reviewer requested. Over SLA - platform#1950 chore: move cron config to jobs/. Ana, waiting 3 h, S, reviewer Dana Blocked: - platform#1938 feat(api): cursor pagination for /v2/invoices. Changes requested Friday, no new commits Stale: - web#842 spike: new chart library. Draft, 19 days idle. Suggest: ask Leo to close it or turn it into an issue New issues without labels: - platform#1957 Webhook signature mismatch after key rotation. Proposed: bug, High, PLAT - web#881 Dark mode toggle resets on refresh. Proposed: bug, Low, WEB - web#882 Add Spanish locale. Proposed: feature, No priority, WEB Dependencies: 3 open, oldest 9 days. Security: web#879 (advisory linked in the PR) 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 Sources: GitHub northwind/platform, northwind/web; Linear PLAT, WEB. Nothing missing. Approval needed: post this to #eng-outer-loop? Reply post, or edit.
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.
レビュー
まだレビューはありません。
