pruff-skills 0.5.6 → 0.7.0
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/cli.mjs
CHANGED
package/package.json
CHANGED
|
@@ -44,11 +44,25 @@ don't guess which one they mean.
|
|
|
44
44
|
service layer. Always pass `--standard` explicitly. Go to `--deep` only if a human
|
|
45
45
|
asks for a deeper look in `#pr-review` — never on your own initiative, and never
|
|
46
46
|
drop back to `light` for a PR that "looks contained."
|
|
47
|
-
4. **
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
47
|
+
4. **Comment the dossier on the PR.** The skill reports a markdown dossier and a link to
|
|
48
|
+
an interactive HTML version. **Post the markdown as the comment body** — that is the
|
|
49
|
+
durable record. Then add the link on its own last line, with the absolute expiry date
|
|
50
|
+
the skill reported:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
🔬 Dossier interactivo (expira 2026-08-14): <url>
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
The link is a presigned URL and expires; the markdown does not. Never post the link
|
|
57
|
+
*instead of* the markdown — a reader on a phone, or anyone opening the PR after the
|
|
58
|
+
link dies, must still get the whole review. Keep the comment to what GitHub renders:
|
|
59
|
+
mermaid, tables, and `> [!WARNING]` blockquotes all work; anything needing CSS
|
|
60
|
+
(`<style>`, `class`, `style=`, `<svg>`, `data:` images) does not.
|
|
61
|
+
5. **Post the summary in `#pr-review`**: the dossier link with its expiry date (or, if the
|
|
62
|
+
upload wasn't available in this session, a written equivalent plus a pointer to the PR
|
|
63
|
+
comment), the highest-severity findings with a concrete failure scenario each ("this
|
|
64
|
+
could be slow" is not a finding), and whether description and code actually match.
|
|
65
|
+
6. **Request a human reviewer** — `gh pr edit <n> --add-reviewer <github-username>`.
|
|
52
66
|
This is a real GitHub review request, independent of Buzz's own (currently broken)
|
|
53
67
|
cross-owner mention system — use it, don't rely on an `@mention` landing.
|
|
54
68
|
|
|
@@ -63,7 +77,8 @@ worse than asking once.
|
|
|
63
77
|
|
|
64
78
|
- **You never approve, request changes, or merge.** `gh pr review` with a verdict is
|
|
65
79
|
out of scope, full stop — your output is a summary plus a review *request*, and the
|
|
66
|
-
verdict is a human's call every time.
|
|
80
|
+
verdict is a human's call every time. Posting the dossier is **not** a verdict:
|
|
81
|
+
`gh pr comment` is expected of you, `gh pr review` is never.
|
|
67
82
|
- **Never push a commit or open a PR yourself.** That's `fixer-shared`'s job.
|
|
68
83
|
- If the PR touches `prisma/schema.prisma` or a migration, say so loudly at the top of
|
|
69
84
|
your summary — it affects 30+ tenant databases and deserves extra scrutiny before
|