From c540e41fe0b6fe021fd73774045423c4f919ebaf Mon Sep 17 00:00:00 2001
From: jinbagi <4094424+jinbagi@users.noreply.github.com>
Date: Fri, 3 Jul 2026 09:53:08 +0900
Subject: [PATCH] docs: switch to pr-based workflow

---
 AGENTS.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index db3a9c72..57758d55 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -72,12 +72,16 @@ Recent commits use concise Conventional Commit-style subjects, for example
 PRs should describe changed resource behavior, list verification commands, and
 include screenshots or recordings for visible UI changes.
 
-After completing and verifying each self-contained unit of work, always commit
-it immediately and push it directly to `origin/master`. Do not defer commits or
-combine multiple completed units into a later commit unless the user explicitly
-requests a different workflow. If the project is configured to maintain a single
-initial release commit, always use `git commit --amend` and force push (`git push -f`)
-to keep the commit history squashed.
+Do not push work directly to `origin/master`. Use a working tree branch for each
+self-contained unit of work. After completing and verifying the unit, commit it
+on that branch, push the branch to `origin`, open a pull request targeting
+`master`, and use the PR merge flow to land it into `origin/master`.
+
+Keep each PR focused on one coherent change. Do not defer completed work into a
+larger later batch unless the user explicitly requests that. After the PR is
+created, enable automatic merge when repository rules allow it; otherwise merge
+through the PR once checks and required review conditions are satisfied. Delete
+the source branch after the PR has been merged.
 
 ## Security And Configuration