From a7d93098989229f3e7d4dd66d30c4cff35da444d Mon Sep 17 00:00:00 2001 From: Mark Schaller Date: Sat, 26 Sep 2026 02:31:22 -0400 Subject: [PATCH] Say where the parity artifacts belong The procedure listed the parity artifacts to produce (the two models, aquery.json, diff.json) but said only that they live "in or beside" the target repo, so where they ended up was up to the agent. Measured in any2bazel-lab: one migration wrote its diff and both models to a session-scoped temp directory, so nothing in the repository showed that it had converged; another kept them at the repo root, gitignored them, and recorded how to regenerate them, unprompted. The preamble now says: at the target repo root beside any2bazel.json, gitignored with a comment naming the regeneration command, not in a temp directory. That makes a migration auditable by default without committing large generated JSON. In the lab's later graphicsgems and lensfun runs with this change, the artifacts were at the root, gitignored, with the regeneration command. Lab-Proposal: P6 Co-Authored-By: Claude Opus 5.5 --- SKILL.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/SKILL.md b/SKILL.md index b39386f..8fdaa3b 100644 --- a/SKILL.md +++ b/SKILL.md @@ -186,8 +186,9 @@ the reference build or bazel. > `python3 "$SKILL_DIR/scripts/extract_bazel.py" …` where `$SKILL_DIR` is this > skill's install location (e.g. `~/.claude/skills/any2bazel`). The artifacts > you *produce* — `model.*.json`, `aquery.json`, `diff.json`, the generated -> `BUILD.bazel`/`MODULE.bazel`, and `any2bazel.json` — live in or beside the -> target repo. +> `BUILD.bazel`/`MODULE.bazel`, and `any2bazel.json` — live in the target repo: +> put the parity artifacts at its root beside `any2bazel.json`, gitignored with +> a comment naming the command that regenerates them, not in a temp directory. > > **Working directory:** run the reference build and `bazel` from the **target > repo root** (the Bazel workspace). Only the `$SKILL_DIR/scripts/*.py` helpers