Agent skill
github-project-reporter
Reads and analyzes GitHub Projects v2 data using gh CLI. Use when listing items by status, extracting high-priority tasks, generating sprint progress summaries, detecting blockers or health issues (unassigned items, overdue items, WIP excess), or producing progress reports.
Install this agent skill to your Project
npx add-skill https://github.com/scizorman/dotfiles/tree/main/modules/home/coding-agent/config/skills/github-project-reporter
SKILL.md
GitHub Project Reporter
This skill defines rules and procedures for read operations, analysis, and report generation on GitHub Projects v2.
Session Initialization: Project Selection
At the start of each session, select the target project.
Step 1: List Projects
gh project list --owner "@me" --format json
Present the list to the user and ask which project to use.
Step 2: Collect Project Metadata
gh project view <NUMBER> --owner "@me" --format json
gh project field-list <NUMBER> --owner "@me" --format json
Retain the Project number, Project ID, and field definitions for the session.
Workflow: List Items by Status
gh project item-list <PROJECT_NUMBER> --owner "@me" --format json
Group and display items by their Status field value. Use the field definitions collected during initialization to resolve option IDs to human-readable names.
For report formats, see references/report-templates.md.
Workflow: Extract High-Priority Tasks
From the item list, filter items where:
- Status is not
Done/Closed(or equivalent) - Priority is
CriticalorHigh(or the highest available options)
Sort by Priority descending, then by creation date ascending (oldest first).
Present as a prioritized task list with issue numbers, titles, assignees, and current status.
Workflow: Sprint Progress Summary
Collect all items in the current sprint or iteration:
gh project item-list <PROJECT_NUMBER> --owner "@me" --format json | \
jq '[.items[] | select(.fieldValues[] | select(.field.name == "Sprint") | .name == "<SPRINT_NAME>")]'
Calculate:
- Total items in sprint
- Completed items (Status = Done or equivalent)
- Completion rate (%)
- Remaining items by status
Use the Sprint Summary template from references/report-templates.md.
Workflow: Health Check
Run all of the following checks and produce a Health Check Report.
Blocker Detection
Items with Status Blocked or with a Blocked label:
gh project item-list <PROJECT_NUMBER> --owner "@me" --format json | \
jq '[.items[] | select(.fieldValues[] | select(.field.name == "Status") | .name == "Blocked")]'
Unassigned Items
Items in progress (Status = In Progress or equivalent) with no assignee:
gh project item-list <PROJECT_NUMBER> --owner "@me" --format json | \
jq '[.items[] | select(.assignees == null or (.assignees | length == 0))]'
Unestimated Items
Items without a Size (or Story Points / Effort) field value:
Filter items where the Size field value is null or empty.
WIP Excess
Count items with Status In Progress. If the count exceeds the WIP limit (ask the user if not configured), flag as warning.
Overdue Items
Items with a due date field (e.g., Due Date) earlier than today and Status not Done:
# Today's date
date +%Y-%m-%d
Filter items where due date < today and status != Done.
Use the Health Check Report template from references/report-templates.md.
Workflow: Progress Report
Generate a narrative progress report combining sprint summary, health check, and recent completions.
Use the Progress Report template from references/report-templates.md.
Notes
- All read operations use
gh project item-listwith--format jsonandjqfor filtering. - Field values are stored as structured objects; always resolve option IDs to names using the field definitions collected during initialization.
- When data is insufficient for a metric (e.g., no Sprint field exists), state clearly that the metric is not available rather than skipping it silently.
- Dates are in ISO 8601 format (
YYYY-MM-DD).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
project-plan-creator
Creates project management plans in Markdown. Use when creating project plans, defining how to manage scope/schedule/risk/communication, or detailing project execution strategy. Primarily for internal projects that build systems, processes, or organizational capabilities.
github-project-operator
Manages GitHub Projects v2 write operations using gh CLI. Use when adding issues or PRs to a project, creating tasks (issues) in a project, updating field values (Status, Priority, Size, Sprint, etc.), creating draft issues, creating fields, or archiving items. Also use at the start of a session when selecting a project to work with.
github-issue-creator
Create GitHub issues with gh CLI, including standard issues and sub-issues linked to a parent issue. Use when creating a new issue, breaking down a larger issue into child issues, or establishing a parent-child relationship between issues. Detect repository issue templates, apply title and body conventions, and create the issue with gh CLI.
github-issue-pr-commenter
Post structured comments to GitHub Issues and Pull Requests with gh CLI. Use when reporting completed work, sharing progress, summarizing investigation results, recording design decisions, proposing implementation plans, asking for feedback, or adding supplementary context to a pull request conversation. Do not use for inline pull request review comments on specific files or lines.
github-pr-creator
Submit changes as a GitHub Pull Request with gh CLI. Covers the full workflow: issue confirmation, branch naming, ghq-based git worktree creation or reuse, commit and push, PR template detection, and PR creation with gh pr create. Use when creating a pull request, opening a PR, starting work on an issue, or cutting a working branch.
project-charter-creator
Use this skill whenever the user wants to create, draft, or improve a Project Charter. Triggers include: any mention of 'project charter', 'charter', 'プロジェクト憲章', 'プロジェクトチャーター', 'プロジェクト企画書', or requests to formally authorize a project, define project scope and objectives, align stakeholders, or establish project governance. Also use when the user says 'プロジェクトの立ち上げ', 'プロジェクトの認可', 'キックオフ文書', or mentions needing to get sponsor approval for a project. This skill covers project charters for any methodology (Waterfall, Agile, Lean Six Sigma) and any domain (IT, construction, marketing, organizational change, product development, etc.). Use this skill even if the user just says 'help me start a project' or 'I need to get alignment on my project'.
Didn't find tool you were looking for?