From fc4217f1cb5dd82ab7c43385249ebc23a8206c3d Mon Sep 17 00:00:00 2001 From: junior Date: Mon, 6 Jul 2026 07:36:10 +0000 Subject: [PATCH] fixup: remove stray leading spaces in run-agent.sh prompts --- .gitea/workflows/scripts/run-agent.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/scripts/run-agent.sh b/.gitea/workflows/scripts/run-agent.sh index 41a1417..6c5f3e4 100755 --- a/.gitea/workflows/scripts/run-agent.sh +++ b/.gitea/workflows/scripts/run-agent.sh @@ -26,7 +26,7 @@ if [ "$MODE" = "comment" ]; then ACTION="You do NOT edit files, create branches, or write a PR description. Respond with your analysis, plan, research, or clarifying questions — your reply becomes a comment on the issue. To hand work to a teammate, end your reply with EXACTLY one line: 'DELEGATE: @' (one of - @junior @senior @lead @qa @intern) — but ONLY when you are ready to hand off AND need nothing further from the + @junior @senior @lead @qa @intern) — but ONLY when you are ready to hand off AND need nothing further from the maintainer. If you are asking @ffaerber to confirm or decide ANYTHING, do NOT include a DELEGATE line; just ask and wait. Never ask for confirmation and delegate in the same reply. Mentioning a teammate in prose does NOT delegate — only the DELEGATE line does. @@ -86,8 +86,8 @@ if [ "$MODE" = "comment" ]; then issue and hands back to @pm (who tells the creator, or in autopilot merges). You do NOT merge. - 'BOUNCE: @' — something needs changing. FIRST spell out, specifically and actionably, exactly what to change (file, label, value, hostname, …), THEN end with the BOUNCE line naming who fixes - it (@junior / @senior / @lead / @intern — usually whoever built it). The automation sends the PR back and - re-verifies with you. After 3 rounds it stops and hands to @ffaerber — so list ALL problems at + it (@junior / @senior / @lead / @intern — usually whoever built it). The automation sends the PR back and + re-verifies with you. After 3 rounds it stops and hands to @ffaerber — so list ALL problems at once, not one at a time. - 'HALT' — the problem is NOT something a dev can fix (the request is ambiguous / needs a human decision). Hands back to @ffaerber.