askill
commit-rule

commit-ruleSafety 95Repository

Guidelines for creating standardized commit messages with gitmoji and issue tracking.

0 stars
1.2k downloads
Updated 2/20/2026

Package Files

Loading files...
SKILL.md

Commit Rule

Overview

All commits must follow a strict format to ensure traceability and standardization.

Rules

  1. Gitmoji: Use gitmojis aggressively to categorize the commit. Use the raw emoji character (e.g., ✨), not the shortcode (e.g., :sparkles:) unless the environment requires it, and NEVER use brackets.
  2. Issue Linking:
    • Extract the issue number from the branch name (e.g., user/#123/feature-x -> #123).
    • Include refs: #<issue-number> in the message.
  3. Co-Author Attribution:
    • Always include the co-author trailer for the AI assistant.
    • Co-Authored-By: gemini-cli <218195315+gemini-cli@users.noreply.github.com>

Format Template

git commit -m "<gitmoji>: <message>. refs: #<issue-number>" -m "Co-Authored-By: gemini-cli <218195315+gemini-cli@users.noreply.github.com>"

Do NOT use brackets [] around the gitmoji.

Examples

  • ✨: Add user login feature. refs: #42

  • 🐛: Fix null pointer exception in auth. refs: #101

  • ♻️: Refactor database connection logic. refs: #88

  • 🤖: Add new AI skill or update agent configuration. refs: #26

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

68/100Analyzed 3/11/2026

Well-structured skill providing clear commit message guidelines with gitmoji, issue linking, and co-author attribution. Actionable with exact command template and examples. However, the skill is highly internal-only (in .gemini/ folder, references specific gemini-cli tool) making it project-specific. Tags are mismatched (database/security) for a commit convention skill. Missing an explicit trigger/when-to-use section."

95
85
45
70
75

Metadata

Licenseunknown
Version-
Updated2/20/2026
Publisherpoteto0

Tags

databasegithubsecurity