copilot-commit-style

Use this skill when the user asks to write, generate, draft, or format a git commit message. It enforces the Conventional Commits specification with mandatory emojis and strict formatting rules.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "copilot-commit-style" with this command: npx skills add nguyenhuy158/skills/nguyenhuy158-skills-copilot-commit-style

Copilot Commit Style Instructions

This skill provides the mandatory rules for formatting git commit messages according to the project's Conventional Commits specification.

Commit Message Format

Every commit message MUST follow this exact format:

<emoji> <type>(<scope>): <description>

[optional body]

[optional footer(s)]

Constraints:

  • Emoji is REQUIRED: Every commit must start with a relevant emoji.
  • Scope is REQUIRED: You must specify a scope in parentheses. Format: type(scope): description.
  • Lowercase Types: <type> must be in lowercase.
  • Separation: A colon and space must follow the scope.
  • Single Line Only: The commit header must be a single line. No newline characters within the header.
  • Length Limit: The entire commit header (including emoji and scope) must be less than 80 characters.

Allowed Types & Emojis

EmojiTypeMeaningSemVer
featNew featureMINOR
🐛fixBug fixPATCH
📝docsDocumentation changesNone
🎨styleFormatting, missing semi-colons, etc.None
♻️refactorCode change that neither fixes a bug nor adds a featureNone
⚡️perfCode change that improves performancePATCH
testAdding missing tests or correcting existing testsNone
👷buildChanges that affect the build system or external dependenciesNone
💚ciChanges to CI configuration files and scriptsNone
🔧choreOther changes that don't modify src or test filesNone
revertReverts a previous commitNone

Note: A BREAKING CHANGE (which triggers a MAJOR version bump) is signaled by adding a ! after the type/scope or by including BREAKING CHANGE: in the footer.


Examples

Correct Format:

  • ✨ feat(auth): add OAuth2 login flow
  • 🐛 fix(api): resolve memory leak in worker
  • 📝 docs(readme): update installation guide
  • ⚡️ perf(db)!: optimized query for user lookup

Incorrect Format:

  • feat: add something (Missing scope and emoji)
  • ✨ feat: add something (Missing scope)
  • feat(ui): add something (Missing emoji)
  • ✨ fix memory leak (Missing type/scope format)
  • ⚡️ fix(stock): very long description that exceeds the character limit of eighty characters per line (Over 80 chars)
  • 🐛 fix(api): first line\nsecond line (Contains multiple lines in header)

Links

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

odoo-code-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

nano-banana-2

Nano Banana 2 - Gemini 3.1 Flash Image Preview

Repository Source
41.9K153inferen-sh
General

qwen-image-2

Qwen-Image - Alibaba Image Generation

Repository Source
41.7K153inferen-sh
General

p-video

Pruna P-Video Generation

Repository Source
41.7K153inferen-sh