@fullstackhouse/cerber 1.6.3 → 1.6.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/runner/prompt.js +3 -3
- package/package.json +1 -1
package/dist/runner/prompt.js
CHANGED
|
@@ -79,8 +79,8 @@ Summary shape:
|
|
|
79
79
|
- \`### 🎯 \` the problem — the symptom someone hit and what it cost them, in plain words. No identifiers yet; a product manager should follow this section. For a PR that fixes nothing, this is the goal instead.
|
|
80
80
|
- \`### 🔧 \` the fix — the cause in a sentence, then what the PR does about it. Name things by what they do; identifiers wait for the sections below.
|
|
81
81
|
- \`### 🧭 \` the impact — first say what merging itself does: it changes what runs, or, for a spec or design document, nothing runs differently and approving it commits to a plan. Then, in two or three sentences with no identifiers: what will be different afterwards, for whom, and what stays the same. When several behaviours change, follow with a short before/after table of what people see, never of code. A reviewer in a hurry stops here.
|
|
82
|
-
- \`### 🧩 \` how the pieces fit —
|
|
83
|
-
- \`### 🔍 \` details —
|
|
82
|
+
- \`### 🧩 \` how the pieces fit — when the PR adds a flow or changes how parts work together, whether built or planned, even inside one module. Only a small internal change skips it. Zoom in through the C4 levels, each under a bold label: **System** (the people and outside systems around ours, and what passes between them), **Modules** (the deployable parts and modules, and who calls or notifies whom), **Inside a module** (the main components of the module where most of the change lives). Show only the levels that changed, and skip one that would just repeat the level above, even for a new flow: a new route to an existing service is the Modules level alone, and a new flow inside one module is usually Inside a module alone. **System** appears only when people or outside systems change. A spec PR draws the parts the plan names. Each level gets one or two plain sentences and one top-down \`\`\`mermaid flowchart (\`flowchart TD\`) of at most about 12 nodes, with plain-language labels in double quotes and each arrow labelled with what passes along it. When an existing flow changes, show "today" and "after" as two subgraphs. Use flowchart syntax, never Mermaid's C4 syntax.
|
|
83
|
+
- \`### 🔍 \` details — what a reviewer needs, not everything decided: names, the choice behind the approach, what the PR's own tests pin down, anything counter-intuitive worth knowing.
|
|
84
84
|
- \`### ⚠️ \` worth knowing — risk, follow-up, breaking change. Skip it when there is none.
|
|
85
85
|
- The emoji and the order are fixed. The words after the emoji are yours: write the heading this PR needs ("### 🎯 Searching an order number returned every order"), and fall back to the plain label ("### 🎯 The problem") only when nothing sharper fits.
|
|
86
86
|
- A small PR gets one or two short paragraphs and NO headings. Headings on a three-line summary are noise.
|
|
@@ -274,7 +274,7 @@ Rules:
|
|
|
274
274
|
- "line" is a line in the NEW version of the file and must appear in the diff. Use null for a file-level comment.
|
|
275
275
|
- "severity" is the finding's merge impact — "blocker" (would not approve with this in; the only tier that blocks), "minor" (should fix, author's call), "nit" (taste), null (not a finding: a question, a note). Grade as if the finding is true; hedge in the reply, never in the grade. A verdict revision must still follow from the worst finding left standing.
|
|
276
276
|
- Your reply is prose to a person, not a changelog. The cockpit already shows what you changed — do not list your own edits back to them.
|
|
277
|
-
- A revision keeps the shape the review is written in: a rewritten summary keeps its \`###\` sections (🎯 the problem, 🔧 the fix, 🧭 the impact, 🧩 how the pieces fit, with
|
|
277
|
+
- A revision keeps the shape the review is written in: a rewritten summary keeps its \`###\` sections (🎯 the problem, 🔧 the fix, 🧭 the impact, 🧩 how the pieces fit, with diagrams for only the levels that changed, 🔍 details a reviewer needs, ⚠️ worth knowing — the ones that earn their place), a rewritten "reasoning" stays one lead sentence plus bullets, and a comment body leads with the finding on its own line and never writes its own grade in — every surface prefixes that from "severity". The division of labor holds too: the summary describes the PR and the verdict's reasoning holds the review's own verification — neither retells the other.
|
|
278
278
|
|
|
279
279
|
Writing style:
|
|
280
280
|
- Plain words, short sentences, no jargon. Someone who has NOT read the diff should follow you.
|
package/package.json
CHANGED