chore(git-standards): forbid emoji in commits and PR titles#266
chore(git-standards): forbid emoji in commits and PR titles#266JacobPEvans merged 2 commits intomainfrom
Conversation
Adds an explicit "Commit & PR Title Style" section to the pr-standards skill (loaded on demand whenever an agent drafts a PR), and a one-line cross-reference bullet in git-workflow-standards. Companion to the soul.md flip in ai-assistant-instructions. Together these eliminate the gap that caused recent automated AI-fix PRs (#263, #257) to land with `🤖` prefixes — soul.md was endorsing gitmoji and neither plugin skill said otherwise. Applies to human, AI-assisted, and bot-authored PRs alike. Conventional- commit prefixes carry the signal. (claude)
There was a problem hiding this comment.
Pull request overview
Adds explicit guidance in the git-standards skills to forbid emoji/gitmoji in commit messages and PR metadata, aligning PR drafting behavior with the repo’s conventional-commit style expectations.
Changes:
- Add a new “Commit & PR Title Style” section to
pr-standardsthat bans emoji/gitmoji and calls for conventional-commit prefixes. - Add a cross-reference bullet in
git-workflow-standardsreinforcing conventional-commit prefixes and no-emoji commit messages.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
git-standards/skills/pr-standards/SKILL.md |
Introduces explicit no-emoji guidance for commits/PR titles (and currently PR descriptions) plus conventional-commit prefix guidance. |
git-standards/skills/git-workflow-standards/SKILL.md |
Adds a branch-hygiene bullet that cross-references pr-standards for commit-message style (no emoji + conventional-commit prefixes). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…hrasing Addresses copilot review feedback (threads VOoy, VOpG, VOpT) on PR #266. Changes: - Rename section header from "Commit & PR Title Style" to "Commit, PR Title & PR Description Style" (header now matches body scope) - Split rule into two parts: emoji ban (commits + titles + descriptions + release notes) and conventional-commit prefix requirement (commit subjects + PR titles only) - Replace ambiguous "Use conventional-commit prefixes only" with "are required at the start of commit subjects and PR titles only" — the original "only" was meant to scope where prefixes apply, but read as if the prefix should be the entire message - Add release notes to the ban for parity with the soul.md update in ai-assistant-instructions PR #604 (claude)
There was a problem hiding this comment.
Code Review
This pull request updates the git workflow and PR standards to mandate conventional-commit prefixes and prohibit the use of emojis in commit messages and PR titles. A review comment suggests refining the language in the PR standards document to improve clarity for automated tools, specifically replacing idiomatic phrasing with more direct language.
Summary
## Commit & PR Title Stylesection togit-standards/skills/pr-standards/SKILL.mdgit-standards/skills/git-workflow-standards/SKILL.mdProblem
Companion to JacobPEvans/ai-assistant-instructions PR #604 (linked below). Until now, neither plugin skill said anything about emoji in commits/PRs, while ai-assistant-instructions'
soul.mdactively encouraged gitmoji. Result: recent automated AI-fix PRs (#257 `🤖 Fix #256: stale guard test fixtures...`, #263 `🤖 Fix #261: make _is_on_main_branch() mockable...`) landed with🤖prefixes.This PR closes the loop on the plugin side so that whenever an agent loads
/pr-standards(the skill that fires precisely when drafting a PR), it sees the no-emoji rule explicitly.Why both repos
soul.mdflip alone could be missed by a session that doesn't auto-load it (rare, but possible)pr-standardsis loaded on demand at the moment of PR creation — perfect last-line-of-defensegit-workflow-standardscross-reference catches commit-message authors who didn't loadpr-standardsScope
Test plan
Related
(claude)