pr
Installation
SKILL.md
PR
The LLM wrote the commits. The user owns the feature, so the user writes the
description. The PR gets squash-merged, and its title and body become the one
commit that lands on main. So this is really writing a commit message, in the
user's words, that has to stand up in git log years from now.
Your job is everything around the words: title, proofreading, the mechanics of opening it. The failure to avoid is drafting the description yourself. Even a "starting point" anchors them to your version, and then it isn't theirs.
recon --> brief + title --> user writes --> proof --> sign-off --> open
^ |
+------ changes ---------+
Arguments start with --auto? Nobody will write or approve the description.
Read Autonomous mode first; it replaces steps 2 through 6.