docs: Update docs on unify workspace style

Author: j3soon

AGENTS.md

@@ -29,6 +29,7 @@
 - Open and self-assign a GitHub issue before starting.
 - Branch naming: `feat/<name>` or `fix/<name>`.
 - Commit messages must follow Conventional Commits and include rationale and sources when relevant.
+- When `template_ws` changes require syncing other workspaces, make a separate minimal "unify" commit (preferred message: `feat: Unify workspaces style`).
 - If code/content is copied, include source and commit permalink in the commit message.
 - Add `Co-authored-by` lines for contributors who helped; avoid force-pushes once review starts.
 

CONTRIBUTING.md

@@ -19,9 +19,10 @@ We welcome all kinds of contributions, including but not limited to bug reports,
 2. Commit description should include as much details as possible. Try to include references you consulted and your rationale behind the changes. This will be essential for reviewers to understand the changes and for future reference. (e.g., [`058ff59`](https://github.com/j3soon/ros2-essentials/commit/058ff598ae705c95516353cd14a71945176c337e))
 3. If copied files from other sources, please include the source in the commit message. If copied from GitHub, include the permalink (link with commit ID) and the branch name. (e.g., [`6a2dac1`](https://github.com/j3soon/ros2-essentials/commit/6a2dac186e1321dc7f7ec961ad22628bffc352d3))
 4. Each commit should be atomic and self-contained.
-5. If anyone helped you during the development, please include them in the commit message using the `Co-authored-by` format (e.g., [`4f9832d`](https://github.com/j3soon/ros2-essentials/commit/4f9832d7a0c4156449d95b3503f9928d2d7de376) due to [this comment](https://github.com/j3soon/ros2-essentials/pull/85#discussion_r2204978905)). These include, but are not limited to, feedback from reviewers, in-person discussions, and pair programming sessions.
-6. Refrain from force-pushes after a reviewer has started reviewing your changes. The only exception is for new contributors when a reviewer has explicitly asked you to rebase your branch or modify commit messages.
-7. Use USDA instead of USD file format whenever possible for better readability and version control. (e.g., [PR#101](https://github.com/j3soon/ros2-essentials/pull/101))
+5. When updating `template_ws` defaults, follow up with a separate unify workspace style commit (preferred message: `feat: Unify workspaces style`) that applies the minimal template-alignment changes across all workspaces. Keep this separate from the template update commit.
+6. If anyone helped you during the development, please include them in the commit message using the `Co-authored-by` format (e.g., [`4f9832d`](https://github.com/j3soon/ros2-essentials/commit/4f9832d7a0c4156449d95b3503f9928d2d7de376) due to [this comment](https://github.com/j3soon/ros2-essentials/pull/85#discussion_r2204978905)). These include, but are not limited to, feedback from reviewers, in-person discussions, and pair programming sessions.
+7. Refrain from force-pushes after a reviewer has started reviewing your changes. The only exception is for new contributors when a reviewer has explicitly asked you to rebase your branch or modify commit messages.
+8. Use USDA instead of USD file format whenever possible for better readability and version control. (e.g., [PR#101](https://github.com/j3soon/ros2-essentials/pull/101))
 
 Use `git log` and search for related commits to understand the commit message format.