Add release skill and local e2e test scripts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: ryu1kn

.claude/skills/release/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: release
+description: Cut a new release of the Partial Diff VS Code extension - guides through version bump, changelog, validation, and publish
+---
+
+Guide the user through cutting a release of the Partial Diff extension. The argument, if given, is the new version number (e.g. `1.4.4`). If omitted, ask the user.
+
+## Execution rules
+
+1. Before starting, create a task for each step below using TaskCreate.
+2. Work through the tasks strictly in order. Mark each task `in_progress` when starting and `completed` when done.
+3. Do NOT skip, reorder, or combine steps.
+4. At each step, confirm with the user before moving to the next.
+
+### 1. Determine scope
+
+- Run `git log v<current-version>..HEAD --oneline` to list commits since the last release.
+- Summarise the user-facing changes (skip purely internal/CI/tooling commits unless they affect the shipped package).
+- Confirm the new version number with the user.
+
+### 2. Bump version
+
+- Update `version` in `package.json` and `package-lock.json`.
+
+### 3. Update CHANGELOG.md
+
+- Add a new entry at the top following the existing Keep a Changelog format.
+- Only include changes relevant to users. Infrastructure-only changes can be omitted or summarised briefly.
+- Use today's date.
+
+### 4. Run pre-publish checks
+
+- Run `npm run prep` (compile:prod + lint + test). All must pass.
+
+### 5. Verify package contents
+
+- Run `npx @vscode/vsce ls` and show the output.
+- Review the file list with the user. Every listed file will be delivered to users — flag anything that looks unnecessary (test files, local config, CI files, etc.).
+- For reference, the v1.4.4 release contained exactly these files:
+  - package.json
+  - README.md
+  - LICENSE.txt
+  - CHANGELOG.md
+  - images/partial-diff_128x128.png
+  - dist/extension.js.map
+  - dist/extension.js
+
+### 6. Test locally
+
+- Install into VS Code: `npm run test:e2e:vscode`
+- Install into Cursor: `npm run test:e2e:cursor`
+- Ask the user to verify that the extension works correctly in both editors and that no errors appear.
+
+### 7. Commit
+
+- Stage `package.json` and `CHANGELOG.md`.
+- Commit with message: `Release v<version>`
+
+### 8. Publish
+
+- Remind the user they need a Personal Access Token for the VS Code Marketplace if they haven't set one up.
+- Run `npx @vscode/vsce publish` — this triggers:
+  - `vscode:prepublish` (production build)
+  - Upload to VS Code Marketplace
+  - `vscode:postpublish` → `tag-release.sh` (creates and pushes git tag `v<version>`)
+- After publish completes, push the release commit: `git push origin main`

package.json

@@ -187,6 +187,8 @@
     "prep": "npm run compile:prod && npm run lint && npm test",
     "test": "mocha",
     "test-mode": "mocha --watch",
+    "test:e2e:vscode": "npx @vscode/vsce package && code --install-extension partial-diff-$(jq -r .version package.json).vsix",
+    "test:e2e:cursor": "npx @vscode/vsce package && cursor --install-extension partial-diff-$(jq -r .version package.json).vsix",
     "vscode:prepublish": "npm run compile:prod",
     "vscode:postpublish": "./tag-release.sh"
   },