From 2d77bcea91d7b8af543b4db4032e759b7e5f6685 Mon Sep 17 00:00:00 2001 From: dal4segno Date: Tue, 24 Mar 2026 16:54:37 +0900 Subject: [PATCH] =?UTF-8?q?chore:=20=EC=BB=A4=EB=B0=8B=20=EB=A9=94?= =?UTF-8?q?=EC=8B=9C=EC=A7=80=20=EA=B7=9C=EC=B9=99=EC=97=90=20chore=20?= =?UTF-8?q?=EC=A0=91=EB=91=90=EC=82=AC=20=EC=B6=94=EA=B0=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - AGENTS.md에 feat, fix와 함께 chore 접두사를 공식 커밋 타입으로 명시 - 씬/프리팹 정리, 에셋 재구성, 기타 유지보수성 작업에 chore를 사용하는 기준을 추가 - 큰 변경의 경우 한국어 bullet 본문을 함께 작성하는 커밋 메시지 규칙을 유지하도록 정리 --- AGENTS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index db88b221..89a1e5a6 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -330,7 +330,9 @@ public class NetworkedComponent : NetworkBehaviour - After Unity-related edits, refresh or compile as needed and check the Unity console before proceeding. - For networked play tests, prefer a temporary non-conflicting test port when needed and restore the default port after validation. - The user has a strong project preference that play mode must be stopped before edits because network ports can remain occupied otherwise. -- Commit messages should follow the recent project history style: use a type prefix such as `feat:` or `fix:` and describe the actual gameplay/UI/system change in Korean with enough detail to understand the scope from the log alone. +- Commit messages should follow the recent project history style: use a type prefix such as `feat:`, `fix:`, or `chore:` and write the subject in Korean so the gameplay/UI/system change is clear from the log alone. +- When the change is substantial, include a blank line after the subject and add Korean bullet points that summarize the work by feature/purpose, similar to commit `0889bb0` (`feat: 드로그 집행 개시 패턴 및 낙인 디버프 추가`). +- Prefer the format `type: 한글 요약` for the subject, then `- 변경 사항` bullet lines for the body. Use `feat:` for feature work, `fix:` for bug fixes, and `chore:` for non-feature maintenance such as scene/prefab cleanup, asset reorganization, or other miscellaneous upkeep. The body should mention key implementation scope, affected systems/assets, and validation or rollback notes when relevant. - All code comments and documentation should be in Korean - Use `[Min()]` attribute for numeric minimums in Inspector - Use `[TextArea]` for multi-line string fields