Skip to content

Commit af1e8d0

Browse files
Copilotdsyme
andcommitted
Task 1: judgment-based engagement, 1-3 issues per run, less prescriptive
Co-authored-by: dsyme <7204669+dsyme@users.noreply.github.com>
1 parent d896864 commit af1e8d0

1 file changed

Lines changed: 4 additions & 8 deletions

File tree

workflows/repo-assist.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -89,15 +89,11 @@ Always do Task 11 (Update Monthly Activity Summary Issue) every run. In all comm
8989

9090
### Task 1: Triage and Comment on Open Issues
9191

92-
Every issue should receive at least one Repo Assist engagement. Prioritise issues that have never been commented on, including old backlog issues.
93-
9492
1. List open issues sorted by creation date ascending (oldest first). Resume from your memory's backlog cursor; reset when you reach the end.
95-
2. For each issue (up to 30 per run; save cursor in memory):
96-
a. Check memory: never commented? Always engage. Already commented? Only re-engage if new human comments have appeared since your last comment.
97-
b. Respond based on type: bugs → ask for a reproduction or suggest a cause; feature requests → discuss feasibility; questions → answer concisely; onboarding → point to README/CONTRIBUTING.
98-
c. Keep comments substantive. Never post vague acknowledgements, restatements, or follow-ups to your own comments.
99-
d. Begin every comment with: `🤖 *This is an automated response from Repo Assist.*`
100-
3. Update memory with comments made and the new cursor position.
93+
2. For each issue (save cursor in memory): prioritise issues that have never received a Repo Assist comment, including old backlog issues. Engage on an issue only if you have something insightful, accurate, helpful, and constructive to say. Expect to engage substantively on 1–3 issues per run; you may scan many more to find good candidates. Only re-engage on already-commented issues if new human comments have appeared since your last comment.
94+
3. Respond based on type: bugs → ask for a reproduction or suggest a cause; feature requests → discuss feasibility; questions → answer concisely; onboarding → point to README/CONTRIBUTING. Never post vague acknowledgements, restatements, or follow-ups to your own comments.
95+
4. Begin every comment with: `🤖 *This is an automated response from Repo Assist.*`
96+
5. Update memory with comments made and the new cursor position.
10197

10298
### Task 2: Fix Issues via Pull Requests
10399

0 commit comments

Comments
 (0)