From 8423a04731e99855983f26cae1a2b320313cf005 Mon Sep 17 00:00:00 2001 From: lucieleblanc Date: Fri, 3 Apr 2026 14:54:39 -0400 Subject: [PATCH] strengthen wording around screenshot upload procedure --- .agents/skills/add-command-spec/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.agents/skills/add-command-spec/SKILL.md b/.agents/skills/add-command-spec/SKILL.md index f1813e01..1fdb1f7a 100644 --- a/.agents/skills/add-command-spec/SKILL.md +++ b/.agents/skills/add-command-spec/SKILL.md @@ -116,7 +116,7 @@ For example, adding support for openshift would be done in a branch called `app- A consistent title convention makes it easy to scan PR history and understand what was added at a glance. -You MUST upload screenshots for each generator into the GitHub PR description. Upload the images to GitHub user attachments using https://github.com/drogers0/gh-image or the workflow described at https://github.com/drogers0/gh-image/blob/edb302620a7888801d8d45f87d4a2c12e10c1704/documentation/github-image-upload-flow.md ; then, use the returned image URLs in the PR description to display the screenshots for each generator. +You MUST upload screenshots for each generator and display them in the GitHub PR description. Upload the images to GitHub user content using https://github.com/drogers0/gh-image or the workflow described at https://github.com/drogers0/gh-image/blob/edb302620a7888801d8d45f87d4a2c12e10c1704/documentation/github-image-upload-flow.md ; then, use the returned user content asset URLs in the PR description to display the screenshots for each generator. Do not commit the screenshots. ## Reference Examples