docs(agents): PR body conventions — bullets, real evidence, exact model attribution - #220
Merged
Merged
Conversation
…el attribution Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
JoshuaVSherman
marked this pull request as ready for review
July 16, 2026 21:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
How to test locally
Docs-only change. Review the rendered AGENTS.md section on the branch:
Expect: the new '### PR body conventions' subsection under '## Pull requests'.
Test evidence
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -34,3 +34,12 @@ A React + TypeScript + Vite front-end for Apperson Auto.
Memory
(Add lessons learned here, one bullet each.)
+
+## Pull requests
+
+### PR body conventions (violations may be machine-rejected)
+
+- Summary: markdown bullet points, one change per bullet — never a run-on paragraph.
+- Test evidence: paste the REAL runner output verbatim (the lines showing pass/fail and test counts), inside a ``` fence — never a description like "all tests passed". If the output has scrolled out of view, re-run the test command and paste what it prints.
+- Test plan: exact commands and manual steps that exercise the change (start command, route/page, what to click, expected visible result) — a green test suite alone is not a plan.
+- Attribution:
--authornames the model actually doing the work. Antigravity/agy sessions are ALWAYS `Antigravity — Gemini 3.5 Flash (Medium)` or `(High)` — never write any other Gemini model name (models misremember their own identity; use this exact string).🤖 Work by Claude Code — Haiku 4.5