From 56c85c357acf515690448d9d6286f2303d3a8893 Mon Sep 17 00:00:00 2001 From: Eyejoker Date: Tue, 31 Mar 2026 04:21:22 +0900 Subject: [PATCH] fix: prevent agents from tagging user during paired review loop --- prompts/claude-paired-room.md | 1 + prompts/owner-common-paired-room.md | 1 + 2 files changed, 2 insertions(+) diff --git a/prompts/claude-paired-room.md b/prompts/claude-paired-room.md index 1a61343..e357773 100644 --- a/prompts/claude-paired-room.md +++ b/prompts/claude-paired-room.md @@ -33,3 +33,4 @@ Push back with evidence when the owner is wrong. Hold your ground when you are r - Stagnation: **Spinning** (same error 3+), **Oscillation** (alternating approaches), **Diminishing returns** (shrinking improvement), **No progress** (discussion without change) — name the pattern and report: **Status**, **Attempted**, **Recommendation** - Implementation, commits, and pushes require agreement from both sides. Either can veto - Keep reviews concise — approve quickly when there is nothing to critique +- Never mention or tag the user (@username) during the owner↔reviewer loop — the system handles escalation automatically. User is only notified when all resolution paths (including arbiter) are exhausted diff --git a/prompts/owner-common-paired-room.md b/prompts/owner-common-paired-room.md index 9b3c36b..3335926 100644 --- a/prompts/owner-common-paired-room.md +++ b/prompts/owner-common-paired-room.md @@ -31,3 +31,4 @@ Challenge the reviewer's reasoning. Point out logical gaps, over-engineering, sc - Stagnation: **Spinning** (same error 3+), **Oscillation** (alternating approaches), **Diminishing returns** (shrinking improvement), **No progress** (discussion without change) — name the pattern and report: **Status**, **Attempted**, **Recommendation** - Implementation, commits, and pushes require agreement from both sides. Either can veto - Implement directly when it makes sense — you have full implementation authority +- Never mention or tag the user (@username) during the owner↔reviewer loop — the system handles escalation automatically. User is only notified when all resolution paths (including arbiter) are exhausted