// Create git commits with emoji prefixes and conventional commit messages. Use when the user wants to commit changes, push code, or asks to use "just pm" command.
Use when debugging event loop hangs, task scheduling issues, call_soon vs call_soon_threadsafe confusion, Future callback timing, _enter_task/_leave_task conflicts, GIL contention patterns, per-step vs per-drive task context, uvloop compatibility problems, sniffio/anyio backend detection failures, streaming backpressure deadlocks, or native runtime context issues on the asyncio thread. Also use when verifying asyncio assumptions via quick Python one-liners.
Strict set of rules in terms of codebase development, design patterns, and best practices. Use when the user wants to develop a new feature or refactor existing code.
Quick reference for building full-stack Databricks Apps with apx (React + FastAPI). Use when working on apx projects, creating routes, adding components, or managing dev servers.
| name | commiter |
| description | Create git commits with emoji prefixes and conventional commit messages. Use when the user wants to commit changes, push code, or asks to use "just pm" command. |
Create well-formatted git commits using the just pm command with emoji prefixes and conventional commit style.
Use ONLY these emojis for commit messages:
| Emoji | Code | Type | Description |
|---|---|---|---|
| ✨ | :sparkles: | feat | New feature or capability |
| 🐛 | :bug: | fix | Bug fix |
| 🔧 | :wrench: | chore | Configuration, tooling, or maintenance |
| 📝 | :memo: | docs | Documentation changes |
| ♻️ | :recycle: | refactor | Code refactoring without behavior change |
| 🎨 | :art: | style | Code style, formatting, structure |
| ✅ | :white_check_mark: | test | Adding or updating tests |
| 🚀 | :rocket: | perf | Performance improvements |
| 🔒 | :lock: | security | Security fixes or improvements |
| ⬆️ | :arrow_up: | deps | Dependency updates |
| 🗑️ | :wastebasket: | remove | Removing code or files |
| 🚧 | :construction: | wip | Work in progress |
Gather context - Run these commands to understand the changes:
git status
git diff --staged
git diff
Analyze changes - Determine the primary type of change:
Compose the message - Format: <emoji> <type>: <short description>
Execute the commit - Run:
just pm "<emoji> <type>: <description>"
Good commit messages:
✨ feat: add user authentication endpoint🐛 fix: resolve null pointer in config parser📝 docs: update API documentation for v2🔧 chore: add commiter skill for git workflow♻️ refactor: simplify error handling logic✅ test: add unit tests for payment module⬆️ deps: bump fastapi to 0.110.0Bad commit messages (avoid these):
fix stuff (too vague)✨ feat: Added the new feature for users (past tense, too long)🎉 party: celebrate (wrong emoji, wrong type)If changes span multiple categories, choose the primary one or suggest splitting into multiple commits. Prefer atomic commits that focus on a single concern.
Before committing, verify:
git diff)