upstream-check

name	upstream-check
description	Check upstream repos for updates. Use when user says "/upstream", "check upstream", "sync with upstream", or wants to see what's changed in the source repos this project was derived from.

Upstream Check

Compare this project against its upstream sources to find valuable updates.

Upstream Repos

Source	Repo	What we use
CSS LSP	toba/go-css-lsp	CSS language server

State Tracking

Last checked SHAs are stored in .last-checked in this skill's directory (JSON format).

Workflow

1. Read the last checked SHAs:

cat .claude/skills/upstream-check/.last-checked 2>/dev/null || echo '{}'

2. Get commits from each upstream since last check:

# CSS LSP
gh api repos/toba/go-css-lsp/commits --jq '.[0:20] | .[] | "\(.sha[0:7]) \(.commit.message | split("\n")[0])"'

Stop at each repo's last checked SHA. If no state exists, show recent 10.

3. For interesting commits, fetch the diff:

gh api repos/OWNER/REPO/commits/SHA --jq '.files[] | "\(.filename)\n\(.patch)"'

4. After evaluation, update the state file with latest SHAs:

cat > .claude/skills/upstream-check/.last-checked << 'EOF'
{
  "toba/go-css-lsp": "SHA"
}
EOF

What to Look For

CSS LSP (toba/go-css-lsp):

• New language features or completions
• Bug fixes
• Performance improvements
• API changes that affect the extension

Output

Summarize findings as:

• Commits worth porting (with rationale)
• Commits to skip (already have, not relevant, etc.)

Then update .last-checked with the latest upstream SHAs.