issue-status

Aggregate active Git branch, recent commits, and open issues into a status summary.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Pjpj42/GridRacer --skill issue-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-status
Source: https://github.com/Pjpj42/GridRacer/tree/main/.claude/skills/issue-status
Command: npx skills add https://github.com/Pjpj42/GridRacer --skill issue-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show current work status by aggregating the active Git branch, recent commits, and open issues to give a quick snapshot of ongoing work.

Core Features & Use Cases

  • Consolidates branch state, recent commits, and open issues to surface work-in-progress for individuals and teams.
  • Supports daily standups and project reviews by presenting a concise status summary.
  • Provides a lightweight view of activity (current branch, last commits, open/closed issues) to aid planning and prioritization.

Quick Start

Run /issue-status in your chat or terminal to display the current branch, recent commits, and open issues.

Frequently Asked Questions about issue-status

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

FAQPage Schema
How do I check current GitHub issues and git branch status for a daily standup?

Check current GitHub issues and git branch status by aggregating your active branch, recent commits, and open issues into a concise summary. This surfaces work-in-progress and activity trends, providing a quick snapshot for daily standups or project reviews.

Can I summarize recent git commits and open issues without switching contexts?

Summarize recent git commits and open issues without switching contexts by parsing the active branch name and querying issues via gh. The tool consolidates this data into a single lightweight view, aiding planning and prioritization without performing destructive actions.

Does this status aggregation work with branch names like issue-123?

Status aggregation works with branch names like issue-123 by parsing the branch name to identify the associated work. It then queries open issues via gh and combines this with recent commit data to present a unified progress snapshot.

What's the best way to track work-in-progress across git branches and GitHub issues?

Track work-in-progress across git branches and GitHub issues by consolidating the current branch state, recent commits, and open issues. This approach surfaces ongoing activity trends for individuals and teams, offering a lightweight view to aid project planning.

Are there limitations to aggregating git branch and issue status for project reviews?

Limitations of aggregating git branch and issue status include its read-only nature, as it performs no destructive actions. It provides a concise summary of current activity but does not modify branches, commits, or issues during the project review process.