rangeLink: Skill for Claude Code

Release Prep

Finish the GitHub tracking artifacts for a release of the VS Code extension after the release lock workflow has run. The lock script (pnpm release:lock:vscode-extension X.Y.Z) creates the QA issue and the dev.to issue and adds them to the release board; this skill creates the remaining cross-repo couimet.github.io article-registration issue, adds it to the board, and reports all three URLs.

Input: X.Y.Z target version (e.g., /release-prep 2.1.0)

Step 1: Verify the release lock completed

The lock workflow must have run first; its console summary prints this skill prompt. Confirm its state:

• packages/rangelink-vscode-extension/qa/release-testing-instructions-vX.Y.Z.md exists
• Its frontmatter contains both qa_issue_url: and devto_issue_url: with real URLs

If either check fails, stop and print: run pnpm release:lock:vscode-extension X.Y.Z first, then re-run this skill.

Step 2: Read the issue URLs from the instructions frontmatter

Extract both URLs from the frontmatter of packages/rangelink-vscode-extension/qa/release-testing-instructions-vX.Y.Z.md:

• QA issue URL: the value of qa_issue_url
• Dev.to issue URL: the value of devto_issue_url

These are the issues the lock script created and already added to the release board.

Step 3: Check for an existing cross-repo issue

The article-registration issue lives in couimet/couimet.github.io. Check for an existing open issue with an exact title match before creating a new one, capturing the URL when one exists:

EXISTING_ISSUE_URL=$(gh issue list \
  --repo couimet/couimet.github.io \
  --state open \
  --search "Register RangeLink X.Y.Z article on the site in:title" \
  --json title,url --limit 100 \
  --jq '.[] | select(.title == "Register RangeLink X.Y.Z article on the site") | .url' \
  | head -1)

The --jq filter selects only an issue whose title EXACTLY matches Register RangeLink X.Y.Z article on the site, and --limit 100 covers the full expected result set; together they guard against an older open issue with a similar title being misidentified as this release's registration issue. If $EXISTING_ISSUE_URL is non-empty, reuse that exact URL for the Step 5 board step and the Step 6 report and skip creation, preserving the skill's re-runnability. Step 4 (creation) runs only when no exact match was found.