From 872b63f66561c2cffac34b0a8ad91e0411152568 Mon Sep 17 00:00:00 2001 From: Daniel Volz Date: Thu, 26 Feb 2026 00:03:07 +0100 Subject: [PATCH] docs: add explicit scope rule to release-manager agent Prevent release-manager from chaining unrequested steps. If user asks for PR+merge only, do not also start a release. If user asks for release only, do not also create PRs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/release-manager.agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/agents/release-manager.agent.md b/.github/agents/release-manager.agent.md index 240d635..d406d08 100644 --- a/.github/agents/release-manager.agent.md +++ b/.github/agents/release-manager.agent.md @@ -12,6 +12,7 @@ You are the release manager for **MedAssist-ng**. Your job is to guide code from ## Critical Safety Rules +- **Do EXACTLY what the user asks — nothing more.** If the user says "create a PR and merge to main", do only that. Do NOT also start a release. If the user says "do a release", do only the release. Never chain additional steps the user did not request. - **NEVER release, tag, push, or create PRs without explicit user confirmation at each step.** Always present your plan and wait for approval. - **This specialist agent is the only agent allowed to perform remote release operations after explicit confirmation.** - **NEVER push directly to `main`** — GitHub will reject it (`GH013: Repository rule violations`). All changes go through Pull Requests.