You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-For an opened issue event, the issue body is empty/whitespace only
21
25
- Has label: `duplicate`, `spam`, or `bot-skip`
22
-
- Already has a comment containing `*Open-CoDesign Bot*`
26
+
- For an opened issue or ordinary labeled issue event, the issue already has a comment containing `*Open-CoDesign Bot*`
27
+
- Exception: a `bot-rerun` label may intentionally force a fresh response
28
+
- For an issue comment event, the new comment is from a bot, empty/whitespace only, or not newer than the latest `*Open-CoDesign Bot*` comment
23
29
24
30
## Project Context
25
31
@@ -38,16 +44,16 @@ Public context: `README.md`, `CLAUDE.md`, `AGENTS.md` if present, package manife
38
44
39
45
## Task
40
46
41
-
1.**Load context progressively**: issue metadata, `README.md`, `CLAUDE.md`, `AGENTS.md` if present, relevant package manifests/lockfiles, then source files related to the report.
42
-
2.**Analyze the issue**: identify the reported workflow, provider, platform, error text, expected behavior, and whether the report is a bug, feature request, or support/diagnostics request.
47
+
1.**Load context progressively**: issue metadata, the current human follow-up comment if present, `README.md`, `CLAUDE.md`, `AGENTS.md` if present, relevant package manifests/lockfiles, then source files related to the report.
48
+
2.**Analyze the issue or follow-up**: identify the reported workflow, provider, platform, error text, expected behavior, and whether the report is a bug, feature request, support/diagnostics request, or a follow-up that updates prior bot assumptions.
43
49
3.**Search related history**: search open/closed issues and recent PRs for the same error text, provider, model family, platform, or subsystem before declaring the issue new.
44
50
```bash
45
51
query_terms="key error/provider/model terms from the issue"
46
52
gh issue list -R "$repo" --state all --search "$query_terms" --limit 20
47
53
gh pr list -R "$repo" --state all --search "$query_terms" --limit 20
48
54
```
49
55
4.**Research the codebase with evidence**: find relevant current code paths. For provider/API issues, trace beyond the surface UI into `apps/desktop/src/main`, `packages/core`, `packages/providers`, and `packages/shared`; account for `pi-ai` adapter behavior when repository code depends on it.
50
-
5.**Respond** with accurate information and post to GitHub.
56
+
5.**Respond** with accurate information and post to GitHub. For follow-up comment events, address the newest human comment directly and avoid repeating the whole initial triage unless it is needed to correct or update it.
0 commit comments