@xera-ai/skills 0.3.0 → 0.4.0

package/package.json

@@ -1,5 +1,8 @@
 {
   "name": "@xera-ai/skills",
-  "version": "0.3.0",
-  "files": ["*.md", "version.json"]
+  "version": "0.4.0",
+  "files": [
+    "*.md",
+    "version.json"
+  ]
 }

package/version.json

@@ -1,6 +1,6 @@
 {
-  "skills": "0.1.0",
-  "compatible_prompts": "^1.0.0",
+  "skills": "0.4.0",
+  "compatible_prompts": "^2.2.0",
   "skill_files": [
     "xera-run.md",
     "xera-fetch.md",

package/xera-exec.md

@@ -16,3 +16,13 @@ The user invoked `/xera-exec <TICKET>`. If no key, ask.
 3. Read the latest run directory: `.xera/{{TICKET}}/runs/<latest>/`. Tell the user the runId.
 
 4. Suggest: "Diagnose this run with `/xera-report {{TICKET}}`."
+
+## Step 5 — Record graph events (v0.6)
+
+After Playwright reporter writes `runs/<RUN_ID>/reporter.json`:
+
+```bash
+bun run xera:graph-record exec <TICKET> --run-id <RUN_ID>
+```
+
+Non-fatal.

package/xera-fetch.md

@@ -32,4 +32,20 @@ If the user did not provide a ticket key, ask: "Which Jira ticket key?" and wait
    - First 200 chars of story
    - Whether AC was found in a separate field
 
-5. Suggest next step: "Generate Gherkin? Run `/xera-feature {{TICKET}}` or run the full pipeline with `/xera-run {{TICKET}}`."
+5. Extract modified areas (v0.6 graph foundation):
+
+   After `story.md` is written, follow the `extract-areas.md` prompt template (located at `packages/prompts/extract-areas.md` in the xera install). The prompt instructs you to read the just-fetched ticket's `summary` and `ac` (from `story.md` frontmatter) and output JSON of the form `{ "modifiesAreas": ["slug", ...] }`.
+
+   Write that JSON to `.xera/<TICKET>/graph-input.json`.
+
+6. Record graph events:
+
+   Run:
+
+   ```bash
+   bun run xera:graph-record fetch <TICKET>
+   ```
+
+   This is non-fatal: if it exits non-zero, log a warning *"Graph event not recorded — run `xera doctor` to rebuild"* but continue. Do not block the fetch flow on this.
+
+7. Suggest next step: "Generate Gherkin? Run `/xera-feature {{TICKET}}` or run the full pipeline with `/xera-run {{TICKET}}`."

package/xera-promote.md

@@ -22,3 +22,11 @@ The user invoked `/xera-promote <TICKET> <PomClassName>`.
    git add shared/page-objects/{{POM}}.ts .xera/{{TICKET}}/
    git commit -m "tests: promote {{POM}} from {{TICKET}}"
    ```
+
+## Step 6 — Record graph events (v0.6)
+
+```bash
+bun run xera:graph-record promote --pom-id <ID> --from <OLD> --to <NEW>
+```
+
+`<ID>` is the sha1 of the POM filename basename (the bin-internal can compute this if `--pom-id` is omitted). Non-fatal.

package/xera-report.md

@@ -128,3 +128,11 @@ After the heal sub-flow finishes (whether it applied, refused, or errored), cont
    - Else run `bun run xera:post {{TICKET}}` (uses REST credentials from `.env`).
 
 8. **Summarize** to the user: overall classification, scenario pass/fail counts, the reproduce command (`bunx xera-internal exec {{TICKET}} --replay=<runId>`), and the Jira comment URL if available.
+
+## Step 9 — Record graph classification events (v0.6)
+
+```bash
+bun run xera:graph-record classify <TICKET> --run-id <RUN_ID>
+```
+
+Non-fatal. Note: TEST_OUTDATED detection ships in v0.6.1 — for v0.6.0 this just emits `run.classified` events with existing 4-bucket classifications.

package/xera-script.md

@@ -44,3 +44,13 @@ The user invoked `/xera-script <TICKET>`. If no key, ask.
 
 9. Summarize: list of files written, count of new POMs, mention any POM that *looked* reusable but didn't quite fit (suggest the user might want `/xera-promote` later).
    Suggest: "Run the test now with `/xera-exec {{TICKET}}`, or do the whole pipeline with `/xera-run {{TICKET}}`."
+
+## Step 10 — Record graph events (v0.6)
+
+Run:
+
+```bash
+bun run xera:graph-record script <TICKET>
+```
+
+Non-fatal as in `/xera-fetch`.