git-get-notification

git-get-notification checks GitHub notifications and recent Issues and PRs for a predefined set of monitored repositories. It solves the problem of staying on top of activity across several repos without manually visiting each one, surfacing what is new and prioritized. It triggers when the user asks to check notifications, see what's new, or check updates on monitored repos. The monitored set includes zilliztech/claude-context, zilliztech/memsearch, zilliztech/mcp-server-milvus, langchain-ai/langchain-milvus, milvus-io/milvus-haystack, zilliztech/milvus-marketplace, and zilliztech/vector-graph-rag.

Execution proceeds in steps. It first determines target repos: a partial-name match if the user names one, otherwise all monitored repos. It then fetches unread notifications per repo with gh api notifications filtered by repository full name and sorted by updated_at, classifying them into high priority (mention, review_requested, assign) shown first with details, and medium priority (author, state_change, comment), while skipping subscribed and CheckSuite notifications as noise. It fetches Issues created in the last 7 days (computing the since date with date -d '7 days ago'), showing only open issues and capping at the 10 most recent per repo. It fetches PRs updated in the last 7 days, showing only open PRs and capping at 10. Output is formatted in Chinese, grouped by repo, ordered high priority, medium priority, recent Issues, then recent PRs, with relative timestamps, a per-repo empty state, and a final summary line counting high/medium notifications, new Issues, and new PRs.

It targets developers and maintainers watching Milvus and Zilliz-related repositories. All queries use gh api, so the gh CLI must be authenticated. Notes specify never marking notifications as read, keeping output concise by prioritizing recency and importance, and adjusting the default 7-day window when the user requests a different range.