القائمة
ALWAYS use when creating git commits. Formats commit messages using Conventional Commits standard with gitmoji emojis.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when choosing between competing technical approaches, recording why an architecture decision (ADR) was made, or revisiting a previous ADR
Translate ambiguous natural language specifications into a formal Intermediate Verification Language (IVL). Use when users provide English specs, requirements, or descriptions of desired behavior and need unambiguous, verifiable specifications. Triggers include phrases like "specify this", "formalize this", "make this unambiguous", "write a spec for", "write specs", "formal specs", "formal specification", "specify this project", "specify this codebase", or when reviewing English specs like SPEC.md files for ambiguities. Also use when asked to create formal specifications for an existing codebase by first exploring it to understand its behavior, then formalizing that behavior into IVL.
Review and improve prompts for Claude using Claude 4 best practices. Use when writing system prompts, optimizing agent instructions, or when the user asks to review/improve prompts with /prompting.
Analyze and fix code quality issues (KISS, YAGNI, DRY, SOLID, etc.). Use when reviewing code quality, refactoring, or checking for code smells.
Use when implementing any feature or bugfix, before writing implementation code
Creates, installs, validates, and formats Agent Skills. Use when developing skills from templates, installing skills from git repositories, linting against the specification, or managing skills across AI coding agents.
| name | conventional-commits |
| description | ALWAYS use when creating git commits. Formats commit messages using Conventional Commits standard with gitmoji emojis. |
| license | MIT OR Apache-2.0 |
Use conventional commit format with gitmoji for all commits in this project.
<type>(<scope>): <emoji> <description>
The emoji comes AFTER the colon, not before the type. Use shortcodes (e.g., :sparkles:) which GitHub renders as emojis.
| Type | Emoji | Code | Description |
|---|---|---|---|
feat | ✨ | :sparkles: | New feature |
fix | 🐛 | :bug: | Bug fix |
docs | 📝 | :memo: | Documentation |
style | 💄 | :lipstick: | UI/style changes |
refactor | ♻️ | :recycle: | Code refactoring |
perf | ⚡ | :zap: | Performance improvement |
test | ✅ | :white_check_mark: | Add/update tests |
build | 📦 | :package: | Build system/dependencies |
ci | 👷 | :construction_worker: | CI configuration |
chore | 🔧 | :wrench: | Maintenance tasks |
revert | ⏪ | :rewind: | Revert changes |
| Emoji | Code | Use case |
|---|---|---|
| 🎉 | :tada: | Initial commit |
| 🔥 | :fire: | Remove code/files |
| 🚑 | :ambulance: | Critical hotfix |
| 🔒 | :lock: | Security fix |
| 🚧 | :construction: | Work in progress |
| ⬆️ | :arrow_up: | Upgrade dependencies |
| ⬇️ | :arrow_down: | Downgrade dependencies |
| 📌 | :pushpin: | Pin dependencies |
| 🏷️ | :label: | Add/update types |
| 💥 | :boom: | Breaking changes |
| ✏️ | :pencil2: | Fix typos |
| 🚚 | :truck: | Move/rename files |
| 🍱 | :bento: | Add/update assets |
| ♿ | :wheelchair: | Accessibility |
| 🔊 | :loud_sound: | Add logs |
| 🔇 | :mute: | Remove logs |
| 🗃️ | :card_file_box: | Database changes |
| 🤖 | :robot: | AI/ML related |
| 🧠 | :brain: | AI/neural network changes |
git commit -m "feat: :sparkles: add user authentication"
git commit -m "fix: :bug: resolve login redirect loop"
git commit -m "docs: :memo: update API documentation"
git commit -m "refactor: :recycle: extract validation logic"
git commit -m "chore: :wrench: update dependencies"
git commit -m "ci: :construction_worker: add GitHub Actions workflow"
Add scope in parentheses for more context:
git commit -m "feat(auth): :sparkles: add OAuth2 support"
git commit -m "fix(api): :bug: handle null response"
For breaking changes, add ! after the type:
git commit -m "feat!: :boom: redesign authentication API"