Print a compact summary of the current repo's gh-pms state — WIP for the user, open issues by status, milestone progress, recent closes, deferred requests. Auto-runs at session start so the agent picks up where the last session left off. User-invocable for an on-demand refresh.

Hand the agent a one-screen snapshot of the project so a new Claude Code session isn't blind to the issue tracker.

When to use

Auto-fires on SessionStart via hooks/session-start.sh — runs once per session
User says "what's going on", "where were we", "give me context", "session refresh"
Before any planning work where current WIP / pipeline state matters

What it does

Resolves the current GitHub repo via gh repo view. Exits silently if not a GitHub repo or gh is not authenticated.
Calls ${CLAUDE_PLUGIN_ROOT}/lib/gh-context.sh <ttl_seconds> — defaults to 300 (5 min cache).
Prints the compact summary to stdout so the harness injects it as context.

The cache lives at ~/.cache/gh-pms/context-<owner>-<repo>.json. Hits return instantly; misses query GitHub and re-cache.

Output shape

text

Forcing a refresh

The skill always re-runs the underlying script; if you want to bypass the cache explicitly:

bash

Or pass 0 as the TTL when calling the lib directly:

bash

Cross-skill contract

gh-status is the deeper, interactive dashboard. gh-context is the lightweight session-warmup variant — use it when you only need to know "what was I doing".
gh-current and gh-advance invalidate this cache after they transition an issue, so subsequent calls reflect the change.

Notes

Output is capped to ~30 lines so it doesn't dominate the conversation context.
Empty buckets are omitted.
Timestamps use the user's local timezone for "started Xh ago" but absolute UTC for cache freshness.