skills.rest
me2resh
me2reshCOMMUNITY
Explore all skills by this author →
Website𝕏@me2reshGitHub

inbox

Aggregates your GitHub tasks and alerts from across managed projects.

489|254|Updated Apr 5, 2026
Search Tags:#productivity#github#pull requests#issue tracking#multi-repo#triage#ci status
One-click install
npx skills add https://github.com/me2resh/apexyard --skill inbox-me2resh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inbox
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/inbox
Command: npx skills add https://github.com/me2resh/apexyard --skill inbox-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The inbox skill eliminates the “where should I look next?” problem by consolidating all PRs, issues, and blockers that require your attention across the managed projects in your ops repo.

Core Features & Use Cases

  • Project-scoped aggregation: Iterates only the repositories listed in apexyard.projects.yaml, avoiding noise from unrelated org repos.
  • Actionable GitHub triage: Surfaces PRs awaiting your review, your PRs with changes requested, PRs ready to merge, issues assigned to you, new comments on your issues, mentions in issues, and PRs failing CI.
  • Clear, gated reporting: Groups results by section, sorts by recency, omits empty sections, and includes clickable URLs for every item.

Quick Start

Run the command /inbox to get a recency-sorted summary of what needs your attention across your managed projects.

Frequently Asked Questions about inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage pull requests and issues across multiple GitHub repositories?▼

To triage pull requests and issues across multiple GitHub repositories, you can aggregate review requests, merge readiness, assignments, and CI failures into a single grouped, URL-complete inbox. This surfaces only items requiring your attention across managed projects.

What is the best way to track urgent PRs and CI failures across my projects?▼

Tracking urgent PRs and CI failures is best handled by consolidating blocker signals and recent activity from a defined project portfolio. This groups PRs failing CI and changes requested by recency to focus your daily workflow.

Can I limit issue tracking to only managed repositories in my ops portfolio?▼

Yes, you can limit issue tracking to managed repositories by reading portfolio paths and resolving projects from a specific registry file. This avoids noise from unrelated org repos by iterating only listed repositories.

How do I aggregate GitHub mentions and comments on my assigned issues?▼

To aggregate GitHub mentions and comments on assigned issues, you consolidate new comments, mentions, and recent activity into sections sorted by recency. Empty sections are omitted to keep the output focused and actionable.

Does multi-repo PR triage handle failures gracefully when a project is unavailable?▼

Multi-repo PR triage handles per-project failures gracefully, ensuring that an unavailable project does not halt the aggregation process. It continues resolving remaining repositories and outputs the successfully gathered inbox items.

Related Skills

Explore More Software Engineering Skills→
me2reshme2resh
489

status

Collect per-project git state, pull requests, and CI check rollups.

Community
Intermediate
tkerseytkersey
66

join

Automate GitHub PR management with CI gates and squash-merge via gh CLI.

Community
Advanced
zizzfizzixzizzfizzix

merge-buddy

Evaluate GitHub pull request merge readiness using labels, reviews, CI, and conflicts.

Community
Intermediate
parcadeiparcadei
3.9k

github-search

Search GitHub code, repositories, issues, and pull requests.

Community
Intermediate