From ddae71537d8ba38bf8fb720ca0d718281924382e Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 3 May 2026 17:32:52 +0100 Subject: [PATCH] docs(agents): require PR descriptions --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 49df9770eb2..92bb8a93452 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -70,6 +70,7 @@ Telegraph style. Root rules only. Read scoped `AGENTS.md` before subtree work. - PR shortlist: `gh pr list ...`; then `gh pr view --json number,title,body,closingIssuesReferences,files,statusCheckRollup,reviewDecision`. - After landing PR: search duplicate open issues/PRs. Before closing: comment why + canonical link. - GH comments with markdown backticks, `$`, or shell snippets: avoid inline double-quoted `--body`; use single quotes or `--body-file`. +- PR create: body required. Include concise Summary + Verification sections; mention issue/PR refs, behavior changed, and exact local/Testbox/CI proof. Never open an empty-body or placeholder-body PR. - PR execution artifacts/screenshots: attach them to the PR, comment, or an external artifact store. Do not add `.github/pr-assets` or other PR-only assets to the repo. - PR review answer must explicitly cover: what bug/behavior we are trying to fix; PR/issue URL(s) and affected endpoint/surface; whether this is the best possible fix, with high-certainty evidence from code, tests, CI, and shipped/current behavior. - When working on an issue or PR, always end the user-facing final answer with the full GitHub URL.