skills.rest
langwatch
langwatchOFFICIAL
Explore all skills by this author →
GitHub

langwatch-kanban

Manage the LangWatch GitHub project board by syncing statuses, moving issues, and assigning work.

3.5k|362|Updated Sep 9, 2023
Search Tags:#gh CLI#Kanban#graphqL#GitHub projects#board sync#Project management#Issue tracking
One-click install
npx skills add https://github.com/langwatch/langwatch --skill langwatch-kanban
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: langwatch-kanban
Source: https://github.com/langwatch/langwatch/tree/main/.claude/skills/langwatch-kanban
Command: npx skills add https://github.com/langwatch/langwatch --skill langwatch-kanban

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping a GitHub Projects board accurate is tedious: closed issues linger in wrong columns, stale items go unnoticed, and manual status updates interrupt development flow. This Skill automates board hygiene for the LangWatch Kanban project so statuses always reflect reality.

Core Features & Use Cases

  • Board Sync: Automatically detect closed or merged issues/PRs whose project status is not Done and update them in bulk.
  • Personal Board View: Show your assigned items grouped by status, skipping completed work, with label context.
  • Stale Item Detection: Flag in-progress items idle for 14+ days, reviews idle for 7+ days, and blocked items without explanation.
  • Move & Assign: Move any issue to a named status or assign an issue to yourself and add it to the board in one command.
  • Use Case: Before a sprint review, run the sync subcommand to sweep all merged PRs into Done, then run stale to surface forgotten in-progress work that needs attention.

Quick Start

Ask the assistant to sync the LangWatch Kanban board and show any stale in-progress items.

Frequently Asked Questions about langwatch-kanban

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

FAQPage Schema
How do I sync a GitHub Projects board with closed issues?▼

Run the sync subcommand, which pages through all project items via the GitHub GraphQL API, finds issues or PRs that are closed or merged but not marked Done, and updates their Status field to Done automatically.

How do I move an issue to a different status on GitHub Projects?▼

Use the move subcommand with the issue number and target status, such as move 123 in-progress. The skill maps the status name to its option ID and updates the item through the updateProjectV2ItemFieldValue mutation.

How can I find stale issues on a GitHub project board?▼

Run the stale subcommand to flag in-progress items with no updates in 14 or more days, in-review items with no PR activity in 7 or more days, and blocked items lacking explanatory comments.

What permissions does the GitHub CLI need for project board automation?▼

The gh CLI must be authenticated with the project scope. If API calls fail, run gh auth refresh -s project to grant the required permission, then retry the command.

Why use python3 instead of jq for parsing GitHub GraphQL responses?▼

Issue titles containing special characters can break jq parsing in shell pipelines. The skill uses python3 with the json module to safely parse paginated GraphQL responses from the gh api command.

Related Skills

Explore More Software Engineering Skills→
botminterbotminter
18

gh

Manage GitHub Projects v2 boards and issue workflows via gh CLI.

Official
Advanced
ronniepinnellronniepinnell

sprint

Review backlog items and prioritize work for upcoming sprints.

Community
Intermediate
mrgeoffrichmrgeoffrich
3

ship-it

Merge reviewed GitHub pull requests and update issue statuses.

Community
Intermediate
duronextduronext
15

ticket

Create and route tickets across Linear, GitHub Issues, or Jira using jig.config.md.

Official
Intermediate