status

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

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill status-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/status
Command: npx skills add https://github.com/me2resh/apexyard --skill status-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the friction of figuring out what’s happening across your active projects by giving you a single, up-to-date status snapshot of git, pull requests, CI, and the in-progress issue.

Core Features & Use Cases

  • Project work visibility: Shows branch, dirty files, recent commits, and ahead/behind status per project.
  • PR + CI health: Summarizes open pull requests and maps CI check states into clear green/yellow/red indicators.
  • In-progress issue mapping: Infers the current issue from the active branch naming convention and surfaces issue state, assignees, and labels.
  • Briefing mode for fast orientation: Produces a compact 4-line “where am I” view suitable for quick session kickoff.

Quick Start

Ask for the current state of all projects by running /status to see git state, open PRs with CI rollups, recently merged PRs, and the in-progress issue.

Frequently Asked Questions about status

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

FAQPage Schema
How do I get a multi-project git status snapshot across my entire portfolio?

To get a multi-project git status snapshot, this Skill iterates projects defined in a root portfolio registry and collects per-project branch state, dirty files, and commit history into a single deterministic, read-only report.

Can I track pull requests and CI check states across multiple repositories at once?

You can track pull requests and CI check states across multiple repositories by using the Skill to summarize open PRs and map CI rollups into clear green, yellow, or red health indicators for each registered project.

How does branch to issue mapping work for tracking in-progress work?

Branch to issue mapping infers the current in-progress issue from your active branch naming convention, then surfaces the issue's state, assignees, and labels directly within the generated project status report.

What is the best way to get a quick project briefing for session kickoff?

The best way to get a quick project briefing is using the briefing mode, which produces a compact four-line view that summarizes your current location and work state across all registered projects for fast orientation.

Does this multi-project status tracker require GitHub CLI to fetch pull request data?

The multi-project status tracker uses the GitHub CLI (gh) to fetch GitHub data when available, but also relies on reading portfolio registry paths from shared bash helpers to iterate through your defined project list.

Are there limitations to the read-only SDLC status report generated by this Skill?

A limitation of the read-only SDLC status report is that it provides a deterministic snapshot without modifying repository state, meaning it strictly surfaces current git, PR, and CI conditions without executing corrective actions.