Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chatondearu/github-kanban-orchestrator
Orchestrates any GitHub repository's backlog via milestones, issues, PRs, and a GitHub Projects (v2) Kanban board. Auto-detects the repo and project at runtime (no hardcoded IDs). Listens to board activity (comments, reviews, labels, assignment, PR merge/close, Status column changes) and reacts.
Passed 12 of 22 test cases with the skill, and 7 of 22 without it.
and 5 more in the full report
5 fixed7 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
During a board event sync, an event of type `review_approved` is detected for pull request #88 which is linked to issue #40. Should the card be immediately moved to 'Done' and the issue closed, or what is the correct board status transition and handoff for an approved PR?
| Checked | Without skill | With skill |
|---|---|---|
| retains the card in In review status upon receiving approval | Missed | Passed |
| hands off the approved PR to a monitoring workflow like babysit to complete merge | Missed | Passed |
The instructions your model reads when the skill loads.
Announce at start: "Using github-kanban-orchestrator skill."
Governs project management on GitHub for the current repository. It does not replace code skills (review-and-ship, babysit, new-branch-and-pr) — it wires them to a Kanban board.
This skill is repo-agnostic: it resolves the owner, repo, project number, and field/option IDs at runtime. Nothing is hardcoded.
gh authenticated: gh auth statusproject scope. If missing: gh auth refresh -s projectgit rev-parse --show-toplevel)Before any board action, resolve identifiers with the helper:
source "$(dirname "$0")/scripts/gh-board.sh" # or run subcommands directly
gh-board env # prints OWNER, REPO, PROJECT_NUMBER, PROJECT_ID, field + option IDs
The helper auto-detects:
OWNER/REPO via gh repo view --json owner,nameStatus, Priority, Size field IDs and their option IDs via gh project field-listIf detection is ambiguous (multiple projects), pass an override:
gh-board env --project-number 2 --owner some-owner
Never paste IDs from another repo. Re-resolve per repository.
test cases passed, vs 7 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.