From 99e6d4f1ad57920631f010a12e96fd22cbfb0e49 Mon Sep 17 00:00:00 2001 From: Andrey Antukh Date: Tue, 8 Sep 2026 16:39:35 +0000 Subject: [PATCH] :books: Forbid hand-editing CHANGES.md in agent guides Adds the hard rule to AGENTS.md and to mem:critical-info: CHANGES.md is generated from GitHub milestones during the release process; it must be updated only via the update-changelog skill flow or on explicit user request. AI-assisted-by: omen-alpha --- .serena/memories/critical-info.md | 1 + AGENTS.md | 3 +++ 2 files changed, 4 insertions(+) diff --git a/.serena/memories/critical-info.md b/.serena/memories/critical-info.md index 117e8ff464..9033a9e74a 100644 --- a/.serena/memories/critical-info.md +++ b/.serena/memories/critical-info.md @@ -15,6 +15,7 @@ You are working on the GitHub project `penpot/penpot`, a monorepo. - Before `gh issue create` → `mem:workflow/creating-issues` (title derivation, body template, labels, Issue Type) - Before `gh pr create` / `gh pr edit` → `mem:workflow/creating-prs` (title format, body structure, "Note:" line) - **Never `git push`, force-push, or modify `git origin`** (or any other remote). The user pushes from their own shell; if a push is required, say so and wait. Never amend a commit that the user has already pushed unless explicitly asked. +- **Never edit `CHANGES.md` by hand.** The changelog is generated from GitHub milestones during the release process; update it only via the `update-changelog` skill flow or on explicit user request. - You have access to the GitHub CLI `gh` or corresponding MCP tools. - Issues are also managed on Taiga. Read issues using the `read_taiga_issue` tool. - Before writing code, analyze the task in depth and describe your plan. If the task is complex, break it down into atomic steps. diff --git a/AGENTS.md b/AGENTS.md index 06507f18d1..a02706f460 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -8,6 +8,9 @@ wait for the user to push. Do not change the remote URL, do not switch SSH↔HTTPS. - **Never amend a commit that has been pushed** unless the user explicitly asks. If the user pushes, treat that commit as final from the agent's side. +- **Never edit `CHANGES.md` by hand** in commits or PRs. The changelog is + generated from GitHub milestones during the release process; update it only + via the `update-changelog` skill flow or on explicit user request. - **Never pipe test output directly to filters** (`| head`, `| tail`, `| grep`, etc.). Always redirect to a file first: `command > /tmp/output.txt 2>&1`, then read/grep the file. This prevents hiding test failures. See `mem:testing` for details.