From bcf77767b2356b4488dec2a81c52659a8b8e920f Mon Sep 17 00:00:00 2001 From: Andrey Antukh Date: Wed, 8 Jul 2026 15:40:17 +0200 Subject: [PATCH] :book: Update ai agents documentation --- .serena/memories/critical-info.md | 6 +++++- AGENTS.md | 15 +++++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/.serena/memories/critical-info.md b/.serena/memories/critical-info.md index 33ccf8a8ad..d0f83b656b 100644 --- a/.serena/memories/critical-info.md +++ b/.serena/memories/critical-info.md @@ -9,7 +9,11 @@ You are working on the GitHub project `penpot/penpot`, a monorepo. # Development workflow -- Commit only when explicitly asked. Commit/PR format + changelog: `mem:workflow/creating-commits`, `mem:workflow/creating-prs`. Issue creation (titles, labels, body templates, Issue Types): `mem:workflow/creating-issues`. +- Commit/PR/issue creation is **on explicit request only**. Before any of these actions, read the relevant memory — don't infer format from prior examples: + - Before `git commit` → `mem:workflow/creating-commits` (subject format, body, `AI-assisted-by: model-name` trailer) + - 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. - 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 08103521e0..8c3e6ba431 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,5 +1,20 @@ # AI AGENT GUIDE +## Hard rules (always apply — no exceptions) + +- **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 to surface the + agent's work (e.g. force-push after an amend), state this in the response and + 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. +- **Read the workflow memory BEFORE the corresponding action**: + - Before `git commit` → `mem:workflow/creating-commits` (commit format, AI-assisted-by trailer) + - Before `gh issue create` → `mem:workflow/creating-issues` (title derivation, body template, Issue Type) + - Before `gh pr create` / `gh pr edit` → `mem:workflow/creating-prs` (title format, body structure, AI note) + Don't infer format from the title of a previous commit/issue/PR — the memory + is the source of truth. + ## CRITICAL: Read module memories BEFORE writing any code Do this **before planning, before coding, before touching any file**: