{"owner":"carloscuesta","repo":"gitmoji","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Gitmoji Guide for AI Assistants\n\n## Purpose\n\nThis guide helps AI assistants understand and use gitmoji convention when creating commits. Using emojis on commit messages provides an easy way of identifying the purpose or intention of a commit with only looking at the emojis used. Gitmoji use emojis to make commit messages more expressive and easier to understand at a glance.\n\n## Official Specification\n\nA gitmoji commit message is composed using the following pieces:\n\n- **intention**: The intention you want to express with the commit, using an emoji from the gitmoji list. Either in the `:shortcode:` or unicode format.\n- **scope**: An optional string that adds contextual information for the scope of the change.\n- **message**: A brief explanation of the change.\n\n### Format\n\n```\n<intention> [scope?][:?] <message>\n\n[optional body]\n```\n\n## Gitmoji reference\n\nFetch all available gitmojis from: https://gitmoji.dev/api/gitmojis.\n\n## Usage Guidelines for AI\n\n### Selecting the correct emoji\n\n1. **Identify the primary purpose** of the commit\n2. **Choose the most specific emoji** that matches the change\n3. **Use only one emoji** per commit for clarity\n4. **Prioritize by impact**: Breaking changes (💥) > Features (✨) > Fixes (🐛) > Refactoring (♻️)\n\n### Examples\n\n```\n✨ feat: Add user authentication system\n\nImplement JWT-based authentication with login and registration endpoints.\nCloses #123\n```\n\n```\n🐛 Resolve null pointer exception in user service\n\nAdded null check before accessing user properties to prevent crashes.\n```\n\n```\n📝 docs: Update installation instructions\n\nAdded step-by-step guide for setting up the development environment.\n```\n\n```\n⚡️ Optimize user query with indexing\n\nReduced query time from 500ms to 50ms by adding composite index.\n```\n\n```\n💥 Update API response format to REST specification\n\nAll API endpoints now return data in a standardized envelope format.\nClients must update their response parsing logic.\n```\n\n## Best Practices\n\n1. **Be atomic**: One emoji, one purpose, one commit\n2. **Write clear subjects**: Keep under 60 characters, imperative mood\n3. **Use the body**: Explain \"why\" not \"what\" for complex changes\n4. **Reference issues**: Include issue numbers when applicable\n5. **Indicate breaking changes**: Use 💥 `:boom:`.\n\n## Resources\n\n- Gitmojis list: https://gitmoji.dev/api/gitmojis\n- Gitmoji website: https://gitmoji.dev/\n- Gitmoji specification: https://gitmoji.dev/specification\n"},"files":{"AGENTS.md":"# Gitmoji Guide for AI Assistants\n\n## Purpose\n\nThis guide helps AI assistants understand and use gitmoji convention when creating commits. Using emojis on commit messages provides an easy way of identifying the purpose or intention of a commit with only looking at the emojis used. Gitmoji use emojis to make commit messages more expressive and easier to understand at a glance.\n\n## Official Specification\n\nA gitmoji commit message is composed using the following pieces:\n\n- **intention**: The intention you want to express with the commit, using an emoji from the gitmoji list. Either in the `:shortcode:` or unicode format.\n- **scope**: An optional string that adds contextual information for the scope of the change.\n- **message**: A brief explanation of the change.\n\n### Format\n\n```\n<intention> [scope?][:?] <message>\n\n[optional body]\n```\n\n## Gitmoji reference\n\nFetch all available gitmojis from: https://gitmoji.dev/api/gitmojis.\n\n## Usage Guidelines for AI\n\n### Selecting the correct emoji\n\n1. **Identify the primary purpose** of the commit\n2. **Choose the most specific emoji** that matches the change\n3. **Use only one emoji** per commit for clarity\n4. **Prioritize by impact**: Breaking changes (💥) > Features (✨) > Fixes (🐛) > Refactoring (♻️)\n\n### Examples\n\n```\n✨ feat: Add user authentication system\n\nImplement JWT-based authentication with login and registration endpoints.\nCloses #123\n```\n\n```\n🐛 Resolve null pointer exception in user service\n\nAdded null check before accessing user properties to prevent crashes.\n```\n\n```\n📝 docs: Update installation instructions\n\nAdded step-by-step guide for setting up the development environment.\n```\n\n```\n⚡️ Optimize user query with indexing\n\nReduced query time from 500ms to 50ms by adding composite index.\n```\n\n```\n💥 Update API response format to REST specification\n\nAll API endpoints now return data in a standardized envelope format.\nClients must update their response parsing logic.\n```\n\n## Best Practices\n\n1. **Be atomic**: One emoji, one purpose, one commit\n2. **Write clear subjects**: Keep under 60 characters, imperative mood\n3. **Use the body**: Explain \"why\" not \"what\" for complex changes\n4. **Reference issues**: Include issue numbers when applicable\n5. **Indicate breaking changes**: Use 💥 `:boom:`.\n\n## Resources\n\n- Gitmojis list: https://gitmoji.dev/api/gitmojis\n- Gitmoji website: https://gitmoji.dev/\n- Gitmoji specification: https://gitmoji.dev/specification\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Gitmoji Guide for AI Assistants\n\n## Purpose\n\nThis guide helps AI assistants understand and use gitmoji convention when creating commits. Using emojis on commit messages provides an easy way of identifying the purpose or intention of a commit with only looking at the emojis used. Gitmoji use emojis to make commit messages more expressive and easier to understand at a glance.\n\n## Official Specification\n\nA gitmoji commit message is composed using the following pieces:\n\n- **intention**: The intention you want to express with the commit, using an emoji from the gitmoji list. Either in the `:shortcode:` or unicode format.\n- **scope**: An optional string that adds contextual information for the scope of the change.\n- **message**: A brief explanation of the change.\n\n### Format\n\n```\n<intention> [scope?][:?] <message>\n\n[optional body]\n```\n\n## Gitmoji reference\n\nFetch all available gitmojis from: https://gitmoji.dev/api/gitmojis.\n\n## Usage Guidelines for AI\n\n### Selecting the correct emoji\n\n1. **Identify the primary purpose** of the commit\n2. **Choose the most specific emoji** that matches the change\n3. **Use only one emoji** per commit for clarity\n4. **Prioritize by impact**: Breaking changes (💥) > Features (✨) > Fixes (🐛) > Refactoring (♻️)\n\n### Examples\n\n```\n✨ feat: Add user authentication system\n\nImplement JWT-based authentication with login and registration endpoints.\nCloses #123\n```\n\n```\n🐛 Resolve null pointer exception in user service\n\nAdded null check before accessing user properties to prevent crashes.\n```\n\n```\n📝 docs: Update installation instructions\n\nAdded step-by-step guide for setting up the development environment.\n```\n\n```\n⚡️ Optimize user query with indexing\n\nReduced query time from 500ms to 50ms by adding composite index.\n```\n\n```\n💥 Update API response format to REST specification\n\nAll API endpoints now return data in a standardized envelope format.\nClients must update their response parsing logic.\n```\n\n## Best Practices\n\n1. **Be atomic**: One emoji, one purpose, one commit\n2. **Write clear subjects**: Keep under 60 characters, imperative mood\n3. **Use the body**: Explain \"why\" not \"what\" for complex changes\n4. **Reference issues**: Include issue numbers when applicable\n5. **Indicate breaking changes**: Use 💥 `:boom:`.\n\n## Resources\n\n- Gitmojis list: https://gitmoji.dev/api/gitmojis\n- Gitmoji website: https://gitmoji.dev/\n- Gitmoji specification: https://gitmoji.dev/specification\n","category":"root","tokens":610}]}