Symptom: @pm (and other agents) often leave two comments on one issue — a hand-written report/answer AND the automation-posted transcript.
Cause: the framework already posts each agent reply as a comment (run-agent.sh:148), but the prompt never says the agent must not ALSO post it via the gitea-api skill. On the daily-report task @pm used gitea-api to POST the report itself, then the automation posted its reply too — duplicate.
Not a re-trigger loop: the !contains(...,'🤖') gate works; only one agent run fired. This is purely a double-post within a single run.
Fix: explicit prompt instruction — on the current thread, agents use gitea-api only to READ or to take an explicit requested action (label/close/merge); the report/answer must be the reply text, not a self-posted comment. Cross-issue posting (e.g. opening a sub-issue) is unaffected.
**Symptom:** @pm (and other agents) often leave two comments on one issue — a hand-written report/answer AND the automation-posted transcript.
**Cause:** the framework already posts each agent reply as a comment (run-agent.sh:148), but the prompt never says the agent must not ALSO post it via the `gitea-api` skill. On the daily-report task @pm used `gitea-api` to POST the report itself, then the automation posted its reply too — duplicate.
**Not a re-trigger loop:** the `!contains(...,'🤖')` gate works; only one agent run fired. This is purely a double-*post* within a single run.
**Fix:** explicit prompt instruction — on the current thread, agents use `gitea-api` only to READ or to take an explicit requested action (label/close/merge); the report/answer must be the reply text, not a self-posted comment. Cross-issue posting (e.g. opening a sub-issue) is unaffected.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Symptom: @pm (and other agents) often leave two comments on one issue — a hand-written report/answer AND the automation-posted transcript.
Cause: the framework already posts each agent reply as a comment (run-agent.sh:148), but the prompt never says the agent must not ALSO post it via the
gitea-apiskill. On the daily-report task @pm usedgitea-apito POST the report itself, then the automation posted its reply too — duplicate.Not a re-trigger loop: the
!contains(...,'🤖')gate works; only one agent run fired. This is purely a double-post within a single run.Fix: explicit prompt instruction — on the current thread, agents use
gitea-apionly to READ or to take an explicit requested action (label/close/merge); the report/answer must be the reply text, not a self-posted comment. Cross-issue posting (e.g. opening a sub-issue) is unaffected.