status-report-table

Generates a status report table from git branches, pull requests, pipeline runs, and board tasks.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill status-report-table-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-report-table
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/status-report-table
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill status-report-table-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Answering "where does the work stand" requires manually collecting branch state, PR status, CI run results, and board task data from multiple sources, then formatting it into a coherent report for the project owner. ## Core Features & Use Cases - Ready-made data calls: Provides exact git and GitHub CLI commands to fetch the current branch, commits beyond main, uncommitted changes, PR draft/mergeable state, pipeline runs, and board task details. - Epic-ordered task table: Takes task order from the epic plan rather than the board, producing a paragraph plus a markdown table with per-task state. - Common-miss guidance: Documents pitfalls such as reading board tasks via API instead of the view subcommand, verifying runs against the current commit tip, and detecting template-only task folders. - Use Case: When the owner asks "what is the status of the epic", run the documented commands to assemble a filled-in table showing each task's number, summary, and state (e.g., "code ready, run success 12m 14s"). ## Quick Start Ask the assistant to report the current status of the epic as a table using the status-report pattern.

Frequently Asked Questions about status-report-table

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

FAQPage Schema
How do I report the status of an epic to a project owner?

Collect the branch, commits beyond main, PR state, latest pipeline run, and board task states, then present them as a paragraph naming the epic plus a markdown table with one row per task. Task order comes from the epic plan, not the board.

How to check pull request state with the GitHub CLI?

Use gh api repos/:owner/:repo/pulls/<number> with a --jq filter selecting draft, state, mergeable, and changed_files fields. This returns whether the PR is a draft, whether it merges with main, and how many files changed.

Why does gh issue view fail when reading a board task?

The view subcommand pulls in legacy project boards, and the host rejects the request, failing the whole call. Read the task with a direct gh api repos/:owner/:repo/issues/<number> request instead, selecting title, state, and labels.

How do I verify a pipeline run matches the current commit?

gh run list shows the latest run on the branch, which may predate the current tip. Compare the run against git rev-parse --short HEAD before citing it, so the report never claims success for a stale commit.

What does a green PR that is still a draft mean for the status report?

A successful run with draft status means the merge is locked by the host. The report's Remaining cell should state that lifting the draft, or a named wait, is what blocks completion.