Skip to content

feat(agents): switch triage nudge prefix to @claude-triage #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bokelley merged 1 commit into from
Apr 24, 2026
Merged

feat(agents): switch triage nudge prefix to @claude-triage #265

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/routines/triage-prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,10 +61,10 @@ If > 0, skip — another session beat you to it.
## Manual nudge — overrides the already-engaged check

If the event context contains a `MANUAL NUDGE:` line, a repo member
explicitly requested triage via `/claude-triage`. **Skip the
explicitly requested triage via `@claude-triage`. **Skip the
already-engaged check** and proceed with full triage.

Modifiers: `/claude-triage execute` / `clarify` / `defer` bias the
Modifiers: `@claude-triage execute` / `clarify` / `defer` bias the
outcome. No modifier = standard logic.

## Already-engaged check — before any expert work
Expand Down
8 changes: 4 additions & 4 deletions .github/workflows/claude-issue-triage.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: Claude Issue Triage Bridge
# Bridges GitHub events to a Claude Code routine's /fire endpoint.
# Two entry points:
# 1. `issues.opened` / `issues.reopened` — automatic triage on new issues.
# 2. `issue_comment.created` with `/claude-triage` in the body — manual
# 2. `issue_comment.created` with `@claude-triage` in the body — manual
# nudge from a repo member, useful when you want the routine to
# (re-)look at a specific issue on demand.
#
Expand Down Expand Up @@ -35,7 +35,7 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 2
# Skip bots always. For comment events: only repo members can nudge,
# and the comment body must contain `/claude-triage`.
# and the comment body must contain `@claude-triage`.
if: >-
github.event.issue.user.type != 'Bot' &&
!endsWith(github.event.issue.user.login, '[bot]') &&
Expand All @@ -44,7 +44,7 @@ jobs:
github.event_name == 'issues' ||
(
github.event_name == 'issue_comment' &&
contains(github.event.comment.body, '/claude-triage') &&
contains(github.event.comment.body, '@claude-triage') &&
(
github.event.comment.author_association == 'OWNER' ||
github.event.comment.author_association == 'MEMBER' ||
Expand Down Expand Up @@ -89,7 +89,7 @@ jobs:
# The already-engaged check should pass this through; the nudge IS
# the explicit request.
if [ "$EVENT_NAME" = "issue_comment" ]; then
nudge_note="MANUAL NUDGE: @${COMMENT_AUTHOR} requested triage via /claude-triage. Comment body (trimmed): \"${COMMENT_BODY_SAFE}\". Treat this as an explicit request; do NOT silent-defer on already-engaged signals — the nudge overrides."
nudge_note="MANUAL NUDGE: @${COMMENT_AUTHOR} requested triage via @claude-triage. Comment body (trimmed): \"${COMMENT_BODY_SAFE}\". Treat this as an explicit request; do NOT silent-defer on already-engaged signals — the nudge overrides."
else
nudge_note=""
fi
Expand Down
Loading