PR Workflow¶
Vibe Code Common Sense works best with small PRs.
Good PR¶
- one checklist item;
- one clear purpose;
- tests or verification;
- docs updated when needed;
- tracker updated with PR number.
Bad PR¶
- multiple unrelated features;
- no verification;
- no tracker update;
- architecture changes hidden inside implementation;
- no explanation of what comes next.
Rule¶
If a PR cannot be explained in two sentences, it is probably too large.