xtdb-github

Applies XTDB conventions for GitHub issues, PRs, milestones, and the 2.x project board.

3.0k|192|Updated Mar 19, 2018
One-click install
npx skills add https://github.com/xtdb/xtdb --skill xtdb-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xtdb-github
Source: https://github.com/xtdb/xtdb/tree/main/.claude/skills/xtdb-github
Command: npx skills add https://github.com/xtdb/xtdb --skill xtdb-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributors to the XTDB repository need consistent rules for filing issues and PRs, placing cards on the 2.x project board, setting milestones and labels, and assigning work — without guessing at project IDs, field IDs, or board conventions each session.

Core Features & Use Cases

  • Board and milestone rules: Defines what goes on the 2.x board, the two tests a milestone must pass (end-user-visible and release-blocking), and how sub-issue parenting works.
  • Cached IDs and gh commands: Provides the project node ID, Status/Stream field and option IDs, issue-type IDs, and ready-to-run gh CLI commands for board edits, milestones, and labels.
  • Chalk integration guidance: Explains when to delegate issue/PR/board work to the chalk plugin's github agent and how to pass XTDB-specific IDs verbatim.
  • Use Case: Before opening a PR in xtdb/xtdb, consult this Skill to decide whether the PR or its surrounding issue carries the board card and milestone, then assign yourself and set Status to In progress using the cached field IDs.

Quick Start

Read this Skill before opening an issue or PR in the xtdb repository and follow its conventions to file the card, set the milestone, and update the board.

Frequently Asked Questions about xtdb-github

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

FAQPage Schema
How do I add an issue to the XTDB 2.x project board?

Add an existing issue or PR with `gh project item-add 13 --owner xtdb --url <url>`. Board Status is set automatically on creation, so you only set it later when picking the card up.

When should a milestone be set on an XTDB issue?

Set the 2-NEXT milestone only if the work is end-user-visible and blocks the next release. Non-blocking work gets the milestone at close time, and internal refactors never get one.

Does a PR go on the XTDB project board or its issue?

If a PR is scoped by a surrounding issue, the issue carries the board card and milestone. Only standalone PRs with no surrounding issue go on the board directly.

How do I find the current 2-NEXT milestone number?

Look it up by name with `gh api '/repos/xtdb/xtdb/milestones?state=open' --jq '.[] | select(.title=="2-NEXT") | .number'` because the number changes on each release while the name stays stable.

Why is an archived card invisible in gh project item-list?

Archived items are hidden from both `gh project item-list` and the GraphQL ProjectV2.items connection. Check via the issue itself using the projectItems query with includeArchived set to true.