@juangadm/pre-post 1.4.0 → 1.5.0

package/skill/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: pre-post
 description: Before/after screenshots for the current PR. Use when the user says "take before and after", "pre-post", "screenshot comparison", "visual diff", "PR screenshots", or after making visual UI changes.
-version: 1.4.0
+version: 1.5.0
 allowed-tools:
-  - Bash(npx -y @juangadm/pre-post@1.4.0 *)
+  - Bash(npx -y @juangadm/pre-post@1.5.0 *)
   - Bash(npx pre-post *)
   - Bash(pre-post *)
 ---
@@ -40,7 +40,7 @@ the Post side. Pass `--no-local-baseline` to turn it off.
 ## Run
 
 ```bash
-npx -y @juangadm/pre-post@1.4.0 pr
+npx -y @juangadm/pre-post@1.5.0 pr
 ```
 
 The version is pinned on purpose: this file describes that release. If the run starts with
@@ -53,12 +53,30 @@ land somewhere they can see. Add `--routes /a,/b` when the user names pages expl
 `--before https://production-url` only if the run reports it cannot work out the baseline
 (it is then saved to `.pre-post.json` for next time).
 
+## Video: Moments
+
+When the change **moves or reacts** (a menu or dialog opening, a hover or focus state, a
+transition, form feedback), also record it: write Moments to a file outside the repo and
+add `--moments <file>`. Static changes need none; screenshots cover them.
+
+```json
+{ "moments": [{ "name": "Open the account menu", "route": "/settings",
+  "steps": [{ "hover": "Account" }, { "click": "Account" }] }] }
+```
+
+Steps are `click`, `hover`, `press`, `type` (`["Email", "a@b.co"]`), `scroll` and `wait` (ms),
+naming targets by the text on screen. One interaction per Moment, under 15s, most important
+first; three at most are recorded. "Couldn't find … on Post" means the target text is wrong:
+fix it from the code and re-run once. Guide: https://github.com/juangadm/pre-post/blob/main/docs/video.md
+
 ## What it posts
 
 The visual changes go at the **top of the PR description**, in a delimited block that
 re-runs replace in place — the author's own text is never touched. If the PR cannot be
 edited (a fork, a read-only token) it falls back to a single sticky comment.
 
+Moments come first, one clip each. If they could not play inline, the PR says why; relay that line.
+
 Each changed route shows **Pre beside Post**, per viewport, full pages in a `<details>`. No
 overlay, no percentage. A page that moved says `Content shifted down 48px`; relay as written. A pure move
 ("Nothing else changed.") shows the full pages with no crop and no `<details>`, by design.
@@ -67,7 +85,8 @@ overlay, no percentage. A page that moved says `Content shifted down 48px`; rela
 
 When anything changed, the command prints `Sheet: <path>`: one image with Pre beside Post for
 every change. If you can send files to the user, send that one file, even when the PR was
-updated. Someone following you from a phone sees it there before they open GitHub.
+updated. Someone following you from a phone sees it there before they open GitHub. Each clip
+is printed as `Video: <path>`; send those too.
 
 ## Rules
 
@@ -102,5 +121,5 @@ updated. Someone following you from a phone sees it there before they open GitHu
 To run on every PR without anyone invoking it, point the user to the GitHub Action guide
 (https://github.com/juangadm/pre-post/blob/main/docs/github-action.md). It posts with GitHub's own token, which also covers work done in cloud sessions.
 
-Login-protected sites: `npx -y @juangadm/pre-post@1.4.0 login https://site` opens a browser
+Login-protected sites: `npx -y @juangadm/pre-post@1.5.0 login https://site` opens a browser
 once; the saved session is reused automatically.