Upstream Change Tracker

Check the two upstream repos that go-css-lsp uses as feature references for new commits, classify changes by relevance, and present a summary.

Upstream Repos

Repo	Default Branch	Derived Into
`microsoft/vscode-css-languageservice`	`main`	Feature reference for `internal/css/analyzer/` (completions, diagnostics, hover, formatting, colors, etc.), `internal/css/parser/`, `internal/css/scanner/`, `internal/css/data/`
`lmn451/css-variables-zed`	`master`	CSS variable workspace indexing reference for `internal/css/workspace/index.go`

Workflow

Step 1: Read Marker File

Read .claude/skills/upstream/references/last-checked.json.

•If the file does not exist → this is a first run. Set FIRST_RUN=true.
•If the file exists → parse the JSON to get last_checked_sha and last_checked_date per repo.

Step 2: Fetch Changes (Both Repos in Parallel)

Run both gh api calls in parallel using the Bash tool.

First Run (no marker file)

Fetch the last 30 commits per repo:

bash

gh api "repos/microsoft/vscode-css-languageservice/commits?per_page=30&sha=main" --jq '[.[] | {sha: .sha, date: .commit.committer.date, message: (.commit.message | split("\n") | .[0]), author: .commit.author.name}]'

bash

gh api "repos/lmn451/css-variables-zed/commits?per_page=30&sha=main" --jq '[.[] | {sha: .sha, date: .commit.committer.date, message: (.commit.message | split("\n") | .[0]), author: .commit.author.name}]'

Also fetch the changed files for each repo's recent commits to classify relevance:

bash

gh api "repos/microsoft/vscode-css-languageservice/commits?per_page=30&sha=main" --jq '[.[].sha]' | jq -r '.[]' | head -30 | while read sha; do gh api "repos/microsoft/vscode-css-languageservice/commits/$sha" --jq '{sha: .sha, files: [.files[].filename]}'; done

(Repeat for other repo.)

Subsequent Runs (marker file exists)

Use the compare API:

bash

gh api "repos/microsoft/vscode-css-languageservice/compare/{LAST_SHA}...main" --jq '{total_commits: .total_commits, commits: [.commits[] | {sha: .sha, date: .commit.committer.date, message: (.commit.message | split("\n") | .[0]), author: .commit.author.name}], files: [.files[].filename]}'

bash

gh api "repos/lmn451/css-variables-zed/compare/{LAST_SHA}...main" --jq '{total_commits: .total_commits, commits: [.commits[] | {sha: .sha, date: .commit.committer.date, message: (.commit.message | split("\n") | .[0]), author: .commit.author.name}], files: [.files[].filename]}'

Fallback: If the compare API returns 404 (e.g. force-push rewrote history), fall back to date-based query:

bash

gh api "repos/{owner}/{repo}/commits?since={LAST_DATE}&sha={BRANCH}&per_page=100" --jq '[.[] | {sha: .sha, date: .commit.committer.date, message: (.commit.message | split("\n") | .[0]), author: .commit.author.name}]'

Step 3: Classify Changed Files by Relevance

Use these mappings to assign HIGH / MEDIUM / LOW relevance to each changed file:

microsoft/vscode-css-languageservice

Relevance	Path Patterns
HIGH	`src/services/css.ts` (completion, hover, diagnostics, formatting, validation, codeActions, colors), `src/parser/css.ts` (parser, scanner, nodes)
MEDIUM	`src/services/lint.ts`, `src/services/pathCompletion.ts`, `src/data/`, `src/languageFacts/*`, `Package.json` (dependency changes)
LOW	`.github/`, `README.md`, `CHANGELOG.md`, `docs/`, `.vscode/*`, `.json` (configs)

lmn451/css-variables-zed

Relevance	Path Patterns
HIGH	`src/*/.rs` (core Rust source — variable indexing, parsing, LSP logic)
MEDIUM	`Cargo.toml`, `tests/**`
LOW	`.github/**`, `README.md`, `extension.toml`, `.gitignore`

Files not matching any pattern → MEDIUM (unknown = worth reviewing).

Step 4: Present Summary

Format the output as follows:

code

# Upstream Changes

## microsoft/vscode-css-languageservice (N new commits since YYYY-MM-DD)

### Commits
- `abc1234` Fix property completion for nested selectors — @author (2025-05-01)
- `def5678` Add support for @starting-style — @author (2025-04-28)

### Changed Files

**HIGH relevance** (directly maps to our analyzer/parser):
- src/services/cssCompletion.ts
- src/parser/cssParser.ts

**MEDIUM relevance** (may affect behavior):
- src/data/webCustomData.ts

**LOW relevance** (infrastructure/docs):
- README.md

**Assessment:** 2 high-relevance changes to completion and parser — worth reviewing for potential incorporation.

---

(repeat for each repo)

---

## Overall Recommendation
(Summarize: how many repos have high-relevance changes, suggest priority order for review)

If a repo has no new commits, show:

code

## repo/name — No new commits since last check (YYYY-MM-DD)

Step 5: Update Marker File

Build the new marker JSON with the HEAD SHA and current date for each repo.

•First run: Write the marker file automatically (tell the user it was created).
•Subsequent runs: Ask the user "Update the last-checked markers to current HEAD?" before writing.

Write to .claude/skills/upstream/references/last-checked.json:

json

{
  "microsoft/vscode-css-languageservice": {
    "last_checked_sha": "<HEAD_SHA>",
    "last_checked_date": "<ISO_DATE>"
  },
  "lmn451/css-variables-zed": {
    "last_checked_sha": "<HEAD_SHA>",
    "last_checked_date": "<ISO_DATE>"
  }
}