Code, PRs, support replies
Ship code, not boilerplate.
Commit message templates, PR descriptions, code-review comments, on-call handoffs. Hotwords you can type from any editor, with snippet bodies that support Markdown.
The problem
What makes developers different.
Engineers spend measurable time retyping the same review comments, PR templates, and incident-update messages. Every team has a wiki with the gold standard - nobody reads the wiki.
Sample library
Hotwords a developers would keep.
A plausible shortlist - build your own from here. Every macro ships editable and deletable; nothing is forced on your library.
/rubber
Explain the change like you would to a rubber duck - one short paragraph.
/pr
Full PR template: summary, test plan, risk, rollback, related issues.
/cr-nit
Not blocking, but: [$CURSOR]
/cr-q
Quick question - why [$CURSOR]?
/oncall
Incident update - time [$TIME], status: [$CURSOR], next update in 15 min.
/commit-fix
fix(component): [$CURSOR]\n\nDetails on what changed and why.
What makes the difference: Nested macros plus [$CALC] let you build PR templates that auto-fill the date, the branch name you have on the clipboard, and a one-shot prompt for the user story.