@wipcomputer/wip-release 1.9.50 → 1.9.52

package/core.mjs

@@ -155,8 +155,10 @@ function gitCommitAndTag(repoPath, newVersion, notes) {
       execFileSync('git', ['add', f], { cwd: repoPath, stdio: 'pipe' });
     }
   }
-  // Use execFileSync to avoid shell injection via notes
-  execFileSync('git', ['commit', '-m', msg], { cwd: repoPath, stdio: 'pipe' });
+  // Use execFileSync to avoid shell injection via notes.
+  // --no-verify: wip-release legitimately commits on main (version bump + changelog).
+  // The pre-commit hook blocks all commits on main, but wip-release is the one exception.
+  execFileSync('git', ['commit', '--no-verify', '-m', msg], { cwd: repoPath, stdio: 'pipe' });
   execFileSync('git', ['tag', `v${newVersion}`], { cwd: repoPath, stdio: 'pipe' });
 }
 
@@ -261,6 +263,24 @@ function checkReleaseNotes(notes, notesSource, level) {
     issues.push('Notes look like a changelog entry, not a narrative. Explain the impact.');
   }
 
+  // Narrative quality: must have at least one paragraph (not just bullets/headers)
+  // A paragraph is 2+ consecutive lines of prose (not starting with -, *, #, |, or ```)
+  const lines = notes.split('\n').filter(l => l.trim().length > 0);
+  const proseLines = lines.filter(l => {
+    const t = l.trim();
+    return !t.startsWith('#') && !t.startsWith('-') && !t.startsWith('*') &&
+           !t.startsWith('|') && !t.startsWith('```') && !t.startsWith('>') &&
+           t.length > 30;
+  });
+  if (proseLines.length < 2) {
+    issues.push('Release notes need narrative, not just bullets. Write at least one paragraph explaining what changed and why it matters. Tell the story.');
+  }
+
+  // Must be substantial (not just a header + bullets)
+  if (notes.length < 200) {
+    issues.push('Release notes are too short (under 200 chars). Every release deserves a story: what was broken or missing, what we built, why the user should care.');
+  }
+
   // Release notes should reference at least one issue
   const hasIssueRef = /#\d+/.test(notes);
   if (!hasIssueRef) {
@@ -299,16 +319,14 @@ export function scaffoldReleaseNotes(repoPath, version) {
 
 **One-line summary of what this release does**
 
-## What changed
-
-Describe the changes. Not a commit list. Explain:
-- What was built or fixed
-- Why it matters
-- What the user should know
+Tell the story. What was broken or missing? What did we build? Why does the user care?
+Write at least one real paragraph of prose. Not just bullets. The release notes gate
+will block if there is no narrative. Bullets are fine for details, but the story comes first.
 
-## Why
+## The story
 
-What problem does this solve? What was broken or missing?
+(Write a paragraph here. What was the problem? What does this release fix? Why does it matter?
+This is what users read. Make it worth reading.)
 
 ## Issues closed
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wipcomputer/wip-release",
-  "version": "1.9.50",
+  "version": "1.9.52",
   "type": "module",
   "description": "One-command release pipeline. Bumps version, updates changelog + SKILL.md, publishes to npm + GitHub.",
   "main": "core.mjs",