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.
{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}
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}
This will produce a nicely formatted comment subject line, e.g. **question (non-blocking):** How did you get this this threshold/default value?
.