diff --git a/git-standards/skills/git-workflow-standards/SKILL.md b/git-standards/skills/git-workflow-standards/SKILL.md
index 1887663..ac4be60 100644
--- a/git-standards/skills/git-workflow-standards/SKILL.md
+++ b/git-standards/skills/git-workflow-standards/SKILL.md
@@ -48,6 +48,7 @@ worktrees with uncommitted changes are NEVER stale. Use `git worktree remove` (n
 - Long-running branches: rebase from main weekly
 - Before PRs: ensure branch is on latest main
 - Never branch from feature branches — always from main
+- Commit messages: conventional-commit prefixes only, no emoji (see `pr-standards`)
 
 | Method | When |
 | --- | --- |
diff --git a/git-standards/skills/pr-standards/SKILL.md b/git-standards/skills/pr-standards/SKILL.md
index b8ce16a..52e531b 100644
--- a/git-standards/skills/pr-standards/SKILL.md
+++ b/git-standards/skills/pr-standards/SKILL.md
@@ -64,6 +64,15 @@ for feedback. Just resolve the thread.
 Exception: explicit requests like
 `@gemini-code-assist review the security implications of this change`.
 
+## Commit, PR Title & PR Description Style
+
+No emoji or gitmoji in commit messages, PR titles, PR descriptions, or
+release notes. Conventional-commit prefixes (`feat:`, `fix:`, `chore:`,
+`docs:`, etc.) are required at the start of commit subjects and PR titles
+only — descriptions and release notes are plain prose.
+Applies to all PRs — human, AI-assisted, and bot-authored automated fixes.
+No `🤖`, no `✨`, no `🐛`. The `type(scope):` prefix carries the signal.
+
 ## GitHub Issue Standards
 
 ### Title Prefixes