Triage: #42 "Export to CSV crashes"
Recommendation: category bug, state needs-info. The issue is unlabeled now. The normal path is needs-triage first, but I think it can go straight to needs-info. Either way, the label change and comment wait for your go-ahead.
What I checked
- Prior rejection: there is no
.out-of-scope/directory, so there is no earlier rejection to surface. - Redundancy: this is a crash report, not a feature request, so an existing implementation doesn't apply.
- Codebase: I couldn't explore it. The working directory isn't a git repo, and I only have a file reader here, with no way to list directories or search. I didn't want to guess at paths. If you tell me where the reports page and its export handler live, I'll trace the code path.
- Reproduction: not attempted. There's no running app or repro data, and the report has no steps I could follow.
Why needs-info
The report is too thin to reproduce or to write a durable agent brief from:
- "Spins forever, then the page goes blank" could be a hung request or a server timeout. It could also be an unhandled client-side exception or a memory blowup on a large dataset.
- "Happens on my laptop" gives no browser, OS or app version.
- It doesn't say whether the export works for smaller reports, other reports or other users.
Draft comment (not posted)
> *This was generated by AI during triage.*
## Triage Notes
**What we've established so far:**
- Clicking Export on the reports page shows a spinner that never finishes, then the page goes blank.
- Reported on the reporter's laptop only; we haven't seen it elsewhere yet.
**What we still need from you (@sam):**
- Which report were you exporting, and roughly how many rows does it have? Does a smaller report or a narrower date range export fine?
- Which browser and version are you using, and which OS?
- Open the browser dev tools (Console and Network tabs) and click Export again. Is there a red error in the Console? Does the export request show a status code, or stay "pending"? Please paste what you see.
- Does it fail every time, or only sometimes? Does it also fail for a teammate or on another machine?
- Which app version or deploy are you on?
Next step: should I apply bug + needs-info and post that comment? Or would you rather go to needs-triage first, or give me the code location so I can try to verify the crash from the source before asking @sam anything?
How it was tried: I installed triage together with the grilling and domain-modeling skills it can call, in a clean temporary folder, and invoked it as a slash command with one pasted issue and no issue tracker connected. Only Skill and Read tools were allowed, so nothing was posted, labelled or closed, the codebase could not be explored and no bug was reproduced. It shows only the recommend step and a drafted comment, and it stops to wait for your go-ahead.
できること
メンテナー向けのワークフローです。各課題（および課題とみなす外部 PR）を、2 つのカテゴリ（bug、enhancement）と 5 つの状態（needs-triage、needs-info、ready-for-agent、ready-for-human、wontfix）で仕分けます。
仕組み
- 要対応の一覧：ラベルなし、
needs-triage、新しい返信のあるneeds-info。 - 1 件について：全文を読み、すでに実装済みでないか確認し、
.out-of-scope/に過去の却下がないか確認します。 - カテゴリと状態を提案し、指示を待ちます。
- 主張を検証：バグを再現する、PR が説明どおりか確認する。
- 詰める必要があれば
grillingとdomain-modelingを実行します。 - 結果を反映：エージェント向け指示書、追加情報のお願い、説明付きのクローズ。同梱のガイドには、長持ちするエージェント向け指示書の書き方と
.out-of-scope/ナレッジベースの使い方があります。
向いている場面
課題が多いプロジェクトのメンテナー。コメント投稿や課題のクローズを行うため、各アクションを確認してください。
高リスク：課題管理を直接操作します：ラベルの付与、コメント投稿（各コメントは「AI 生成」の注記で始まります）、課題のクローズ。バグや外部 PR では、バグの再現や PR のチェックアウトとテスト実行を行うことがあり、未確認のコードを実行することになるため、信頼できない PR はサンドボックスやクリーンなクローンで扱ってください。リポジトリにファイル（`.out-of-scope/`、用語集や ADR の更新）も書き込みます。先に提案して指示を待つ作りですが、承認する前に各アクションを確認してください。課題管理のラベル対応と `grilling`・`domain-modeling` が必要です。 1 回試用しました。貼り付けた課題 1 件のみで、課題管理は未接続、ファイル書き込みやシェルのツールもなし。確認できたのは分類の提案とコメント案の作成までです。コメント投稿、ラベル付与、クローズ、バグ再現、PR のチェックアウトは行っていません。