Track GitHub issues and initiatives across multiple repositories. Categorized, prioritized, and synced to your local task file.
Pulls your open issues from every repo you care about, buckets them by product area or team using your label and project mappings, and highlights what actually needs PM attention—not just “everything assigned to you.”
Parallel subagents fetch repos concurrently, so scaling to five or ten repositories doesn’t turn into a long serial crawl. The output syncs into a local task file (for example ACTIVE.md) so your editor, skills, and weekly planning all read the same source of truth.
pm-action labelAny issue tagged for PM follow-up surfaces first—decisions, reviews, or unblock requests that shouldn’t wait for the next staff meeting.
Issues assigned to you that changed in the last 48 hours: new comments, status moves, or linked PRs—so you respond while context is still fresh.
Epics or parent issues with no activity for 14+ days get called out before they silently drift off the roadmap narrative.
Threads with activity since your previous run are marked so you don’t miss a ping buried in a repo you don’t visit daily.
Reads repo list, label-to-category maps, filters for open state, and optional team-specific queries so the scope matches how you actually work.
Queries GitHub for issues across all configured repositories at once, respecting rate limits and authentication from your environment.
Assigns each issue to a bucket, merges cross-repo duplicates when titles or links align, and sorts by priority and recency.
Applies the flagging rules—labels, assignment + recency, staleness, new comments—to produce an “needs you” short list on top of the full inventory.
Writes a categorized markdown (or structured) report and updates your local task file so standups and planning pick up the same snapshot.
Clone the repo and start using this skill in under 60 seconds.