From 037c691fb4dedf135fa436d8c8a34d957e3069cc Mon Sep 17 00:00:00 2001 From: A <258483684+la14-1@users.noreply.github.com> Date: Mon, 9 Feb 2026 03:44:48 -0800 Subject: [PATCH] fix: Remove canned acknowledgment comment from community-coordinator (#73) Skip the generic "thanks for reporting" boilerplate and go straight to categorizing and investigating the issue. Agent: team-lead Co-authored-by: A <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) --- .claude/skills/setup-trigger-service/refactor.sh | 2 -- 1 file changed, 2 deletions(-) diff --git a/.claude/skills/setup-trigger-service/refactor.sh b/.claude/skills/setup-trigger-service/refactor.sh index 40b82656..e90cde23 100755 --- a/.claude/skills/setup-trigger-service/refactor.sh +++ b/.claude/skills/setup-trigger-service/refactor.sh @@ -81,8 +81,6 @@ Create these teammates: 6. **community-coordinator** (Sonnet) - FIRST TASK: Run `gh issue list --repo OpenRouterTeam/spawn --state open --json number,title,body,labels,createdAt` - - For EVERY open issue, immediately post an acknowledgment comment: - gh issue comment NUMBER --body "Thanks for reporting this! Our automated maintenance team is looking into it. We'll post updates here as we investigate." - Categorize each issue (bug, feature request, question, already-fixed) - For bugs: message the relevant teammate to investigate * Security-related → message security-auditor