Choose one emoji prefix that reflects a change’s primary intent, then write concise commit messages or pull request titles. The skill also prompts a cleanup review before committing and explains how to preserve history after a PR is opened.
Use when preparing, reviewing, or suggesting git commit messages or pull request titles, or before creating a commit.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Commit messages and PR titles must be prefixed with exactly one emoji that describes the primary intent of the change.
Prefer the most user-visible category when a commit spans multiple areas.
🐛 Fix a bug.✨ New user-facing feature. Use this only for a meaningful feature users would actively want to try. Use it sparingly. If the change is incremental rather than substantial, prefer 👌. Use only when there is a frontend change.👌 New user-facing addition to an existing feature, such as a new option or small capability. Use only when there is a frontend change.🔧 New internal implementation. Use when the change is mostly internal and not directly noticeable by end users.♻️ Refactoring. Use when behavior stays effectively the same and the main goal is code cleanup or restructuring.💅 UI or UX update. Use when the main value is visual polish, interaction quality, or layout improvements.📝 Blog or documentation update.Always check the diff and remove debug logs, temporary files, commented-out experiments, and other temporary artifacts before creating a commit.
Never amend commits that are already part of an opened PR. Push follow-up fixes as new commits so review history and existing comments remain stable.
Use a concise imperative or descriptive title after the emoji:
🐛 Fix workspace invite redirect
🔧 Add billing sync worker
♻️ Simplify block schema helpers
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use this skill to build React frontend components that follow the project’s UI conventions. It guides layout choices, reuse of shared UI primitives, conditional Tailwind classes, prop ordering, and the organization of hooks, handlers, and derived values.
Use this skill to refresh the project’s available OpenAI and Anthropic model lists. It checks model IDs against models.dev, adds newer entries at the top while retaining older ones for compatibility, and updates image URL support patterns when needed.
Use this skill to design and implement purposeful web animations. It helps choose easing and duration for common interactions, improve performance by animating suitable properties, and support people who prefer reduced motion, with practical guidance for CSS and JavaScript approaches.