Instruction file imported from unbound-app/autosupport (.github/instructions/commit-messages.instructions.md). Copyright stays with the author.

Commit Message Format

Name: commit-messages
Author: unbound-app

Follow the Conventional Commits specification for all commit messages.

Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Use Case
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation changes
`style`	Formatting, no logic change
`refactor`	Code restructuring, no behavior change
`test`	Adding or updating tests
`chore`	Maintenance, dependencies, build changes
`perf`	Performance improvements
`ci`	CI/CD changes
`build`	Build system changes
`revert`	Reverting previous commit

Description Rules

Use imperative mood: "Add", "Fix", "Update", "Remove"
IMPORTANT: Subject line must be under 72 character
No period at end
Be specific about what changed
Avoid vague words: "various", "some", "minor", "stuff"

Body (Summary) Formatting

If a body is definitely needed:

Separate from subject with a blank line
IMPORTANT: Wrap lines at 72 characters
Explain what and why, not how
Reference issues/Jira task if relevant (e.g., "Fixes #123", "Related to #456", "Resolves ABC-789")
Can be multiple paragraphs

Breaking Changes

Indicate breaking changes with:

Exclamation mark before colon: feat!: remove deprecated API
Footer: BREAKING CHANGE: previous tokens are no longer valid

Common Scopes (This Project)

(deps) - dependency updates
(deps-dev) - dev dependency updates
No scope - most other changes

Examples

Change	Good	Bad
New API endpoint	`feat(api): add user preferences endpoint`	`Added new stuff`
Fix null reference	`fix: handle null user in auth middleware`	`Fixed bug`
Update README	`docs: clarify installation steps for Docker`	`Update README`
Rename variable	`refactor: rename userId to accountId for clarity`	`Refactoring`
Upgrade dependency	`chore(deps): bump zod from 4.3.4 to 4.3.5`	`Updated packages`
Add unit test	`test: add coverage for PaymentService edge cases`	`Tests`

Full Example

fix: resolve race condition in user auth

Prevents race condition during simultaneous login attempts.
Multiple concurrent authentications were causing session
corruption and authentication failures.

Fixes #123

BREAKING CHANGE: session tokens are now single-use only

Anti-Patterns

Pattern	Problem	Correct Form
`fix: added...`	Past tense	`fix: add...`
`fix: adding...`	Present continuous	`fix: add...`
`fix: add feature.`	Trailing period	`fix: add feature`
`add feature`	Missing type	`feat: add feature`
`fix: fix bug`	Vague	`fix: handle null in X`
72+ char subject	Too long	Keep under 72 chars
body line >72 chars	Hard to read	Wrap at 72 chars
`✨ feat: add`	Emoji in subject	`feat: add`

Multi-line Messages

git commit -m "feat: add payment validation" -m "Validates amount is positive and currency is supported." -m "Closes #123"

Language

ALWAYS write commit messages in English regardless of conversation language.

{ "ocm": "1", "id": "unbound-app-autosupport-commit-messages-instructions", "kind": "skill", "name": "commit-messages", "description": "Commit message formatting rules following Conventional Commits specification", "publisher": "unbound-app", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Commit message formatting rules following Conventional Commits specification" ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/unbound-app/autosupport", "path": ".github/instructions/commit-messages.instructions.md", "ref": "0c435b2e7e359d446186c4ffc49cfc9fb4311ab7", "url": "https://github.com/unbound-app/autosupport/blob/0c435b2e7e359d446186c4ffc49cfc9fb4311ab7/.github/instructions/commit-messages.instructions.md", "key": "unbound-app/autosupport/.github/instructions/commit-messages.instructions.md" }, "applies_to": "**" }, "instructions": "# Commit Message Format\n\nFollow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for all commit messages.\n\n## Structure\n\n```\n<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n| Type | Use Case |\n| ---------- | ---------------------------------------- |\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation changes |\n| `style` | Formatting, no logic change ", "cost": { "context_tokens": 996 } }

commit-messages

About