Raycast Snippets for Conventional Comments & Commits
I’ve been using Raycast for the past couple years on my MacOS computers for keyboard-based hotkeys/launching/etc. It also has excellent snippet/text-expansion support.
We were discussing at work how to better structure feedback on PR/code reviews, and I shared how I use Raycast to make it easier to adhere to convention/readability/clarity: dedicated snippets. If you structure your communication with others (especially in a remote environment like we have at Shopify) consistently, then you reduce ambiguity and miscommunication and speed up everyone.
Based on Raycast Dynamic Placeholders and the concepts outlined in Conventional Commits and Conventional Comments, here are the snippets I’m using with Raycast:
{argument name="type" options="feat, fix, build, chore, ci, docs, perf, refactor, revert, style, test" default="feat"}{argument name="(scope)" default=""}{argument name="breaking?" options=":, !:" default=":"} {cursor}
Conventional Commit easy-install to Raycast
This will produce a nicely formatted commit title, e.g. feat(editor): Add hover state to graph nodes
.
**{argument name="label" options="praise, nitpick, suggestion, issue, todo, question, thought, chore, note" default="question"}:({argument name="decoration" options="non-blocking, blocking, if-minor" default="non-blocking"}):** {cursor}
Conventional Comment easy-install to Raycast
This will produce a nicely formatted comment subject line, e.g. **question (non-blocking):** How did you get this this threshold/default value?
.
Reference
- Blog
- tools, code-snippets, communication, software-engineering
-
Permalink to
2025.BLG.030
- Edit
← Previous | Next → |
Winter's Last Gasps: Morning Sun Breaks Through | Craig Mod is Running Another Pop-Up Newsletter |