issue-board

Fetches open issues from GitHub Projects v2 and renders them as grouped terminal tables.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/quanthubbr/tron-claude-config --skill issue-board-quanthubbr
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: issue-board
Source: https://github.com/quanthubbr/tron-claude-config/tree/main/managed/skills/issue-board
Command: npx skills add https://github.com/quanthubbr/tron-claude-config --skill issue-board-quanthubbr

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill requires rich.

What problem does it solve? Developers lose track of what to work on next when issues pile up across repositories in a GitHub Project board. This Skill pulls your assigned open issues, classifies the ones the board does not classify (type, priority, difficulty), and renders them as grouped terminal tables so you can decide what to pick up first. ## Core Features & Use Cases - Board Fetching via gh CLI: Reads any GitHub Projects v2 board through the GraphQL API, caching results per board so different boards never mix. - Agent-Assisted Classification: The agent assigns type, priority (P0โ€“P3), and difficulty (1โ€“3) to unclassified issues; values already set on the board always win, and suggestions are marked with ~. - Grouped, Filterable Tables: Renders issues grouped by type, priority, difficulty, status, repo, or a custom board field, with filters and an optional rich-based renderer with colors and clickable issue links. - Use Case: Ask "what do I have to do?" and get a table of your open issues ranked by priority and difficulty, plus a recommendation of which issue to tackle first. ## Quick Start Ask the agent to show your open issues from the GitHub Project board, for example: "show my issues ranked by priority and difficulty."

Frequently Asked Questions about issue-board

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

FAQPage Schema
How do I list my open GitHub Project issues in the terminal?โ–ผ

Run node board.mjs fetch to cache the board, then node board.mjs render to print grouped tables of your assigned open issues. Use render.py instead for colored output with clickable issue links via the rich package.

How do I group or filter GitHub issues by priority or difficulty?โ–ผ

Pass --por tipo, prioridade, dificuldade, campo, status, or repo to the render command to change grouping. Filters like --prioridade P0,P1, --dificuldade facil, --tipo bug, --repo nome, and --status ready accept comma-separated values matched case- and accent-insensitively.

What are the requirements to read a GitHub Projects v2 board from the CLI?โ–ผ

You need Node 18+, the GitHub CLI installed, and authentication with the read:project scope via gh auth login -s read:project. You also need a config.json with the board owner and projectNumber, or pass --owner and --project-number as flags.

Why does the issue board fetch fail with an auth error?โ–ผ

Exit code 2 means gh is not authenticated or the token lacks the read:project scope. Run gh auth login -s read:project, or gh auth refresh -s read:project if the message mentions scopes, then retry the fetch.

Does the agent's classification overwrite fields set on the board?โ–ผ

No. Values already filled in the board's Priority or Size fields always take precedence in the rendered table. The agent's suggested priority and difficulty only appear for empty fields, marked with a tilde.

Can I view issues assigned to someone else or the whole board?โ–ผ

Yes. Use --user login to see another person's issues or --all to render the entire board instead of only your assigned issues. These flags work with both the pending and render commands.