From 1abcb81d5c9bd51476b3a22bfbe3ec0d7411eef9 Mon Sep 17 00:00:00 2001 From: Arne Roomann-Kurrik Date: Tue, 10 Nov 2026 13:38:58 -0800 Subject: [PATCH] docs(shots): link uploaded shots in the pull request description The ArchCode pull request page selects shots from Shots links in the PR description instead of matching uploads by branch name (ArchAstro/firstlanding#22847). Tell agents to put the upload's review URL in the description, and how to pin one run. Co-Authored-By: Claude --- plugins/antigravity/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/claude/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/codex/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/copilot/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/cursor/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/grok/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/opencode/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ plugins/pi/skills/shots/SKILL.md | 22 ++++++++++++++++++++++ shots/SKILL.md | 22 ++++++++++++++++++++++ 9 files changed, 198 insertions(+) diff --git a/plugins/antigravity/skills/shots/SKILL.md b/plugins/antigravity/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/antigravity/skills/shots/SKILL.md +++ b/plugins/antigravity/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/claude/skills/shots/SKILL.md b/plugins/claude/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/claude/skills/shots/SKILL.md +++ b/plugins/claude/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/codex/skills/shots/SKILL.md b/plugins/codex/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/codex/skills/shots/SKILL.md +++ b/plugins/codex/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/copilot/skills/shots/SKILL.md b/plugins/copilot/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/copilot/skills/shots/SKILL.md +++ b/plugins/copilot/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/cursor/skills/shots/SKILL.md b/plugins/cursor/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/cursor/skills/shots/SKILL.md +++ b/plugins/cursor/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/grok/skills/shots/SKILL.md b/plugins/grok/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/grok/skills/shots/SKILL.md +++ b/plugins/grok/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/opencode/skills/shots/SKILL.md b/plugins/opencode/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/opencode/skills/shots/SKILL.md +++ b/plugins/opencode/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/plugins/pi/skills/shots/SKILL.md b/plugins/pi/skills/shots/SKILL.md index a657610..40d5dd8 100644 --- a/plugins/pi/skills/shots/SKILL.md +++ b/plugins/pi/skills/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of diff --git a/shots/SKILL.md b/shots/SKILL.md index a657610..40d5dd8 100644 --- a/shots/SKILL.md +++ b/shots/SKILL.md @@ -526,6 +526,28 @@ is `auto` (including the unset default in 0.56.8 and later). Let the Stop hook handle automatic session uploads; an absent settings row on an older CLI is not an automatic-upload preference. +### Link the shots in the pull request description + +The ArchCode pull request page shows shots only when the PR description links +them. It does not match uploads by branch name, so an upload that is not +linked does not appear on the PR. When the work has a PR, put the review URL +in its description: + +```markdown +Shots: https://archdev.ai/shots/// +``` + +- This is the review URL `upload` prints (`url` under `--json`). After an + automatic upload, whose output you do not see, build it from the `origin` + repository and the feature name. +- A feature link shows every uploaded run of that feature. To show one run, + link a shot's permalink from the Shots page instead + (`https://archdev.ai/shots////runs//`). +- The link must be an `https://archdev.ai` URL and name the PR's head + repository; for a PR from a fork that is the fork. +- Add the link when you open the PR. If the shots are uploaded later, edit + the description then. + ## 7. User stories A user story is a scripted walk through the product from a user's point of