skills/github-project-guide/SKILL.md
Managing items in GitHub Projects v2. Query project items, reorder them, and resolve project IDs. Use when working with GitHub project boards or reordering items in a project.
npx skillsauth add jitsusama/agentic-harness.pi github-project-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
GitHub Projects v2 uses a GraphQL API for managing project items and their positions.
PVT_kwD...PVTI_lAD...List items in a project:
gh project item-list <project-number> --owner <owner> --format json \
| jq '.items[] | {number: .content.number, id: .id, title: .title}'
Or use the helper script:
./scripts/query-project-items.sh <owner> <project-number>
Use the updateProjectV2ItemPosition mutation to reposition an
item within a project:
gh api graphql -f query='
mutation {
updateProjectV2ItemPosition(input: {
projectId: "PVT_kwD..." # Project node ID
itemId: "PVTI_lAD..." # Item to move
afterId: "PVTI_lAD..." # Position after this item
}) {
clientMutationId
}
}'
Or use the helper script:
./scripts/reorder-project-item.sh <project-id> <item-id> [after-id]
afterId is optional; omit it to move the item to the topafterId for bulk reorderingResolve a project number to its node ID.
For organization projects:
gh api graphql -f query='
query($login: String!, $number: Int!) {
organization(login: $login) {
projectV2(number: $number) {
id
title
}
}
}' -f login="ORG" -F number=NUMBER
For user projects:
gh api graphql -f query='
query($login: String!, $number: Int!) {
user(login: $login) {
projectV2(number: $number) {
id
title
}
}
}' -f login="USER" -F number=NUMBER
Or use the helper script:
./scripts/get-project-id.sh <owner> <project-number>
The script tries organization first, then falls back to user.
Scripts are in the scripts/ directory relative to this skill.
Each accepts --help for usage information. They wrap the GraphQL
calls above with error handling and formatted output.
development
Structure of a quest README and the documents that live under it: frontmatter shape, the four core and four optional body sections, emoji glyphs, ID format, alias notation, Cast bullets and Journey entries. Use when writing or editing a quest README, a plan, research, brief or report document under a quest. Pairs with quest-convention for choices like kind, promotion and reordering. Follow the prose-standard for voice.
tools
Operational conventions for the quest system: when to use a quest versus a subquest versus a sidequest, when to scaffold a plan or research document, how to reorder priorities, when to add optional sections, when to conclude versus retire, the resuscitate pattern. Use when driving the quest tool, deciding kind, promoting or parking work, or organising a project as quests. Pairs with quest-format for the on-disk shape.
development
Markdown structure rules: Title Case headings with their exceptions, the line-width target and its legitimate exceptions, reference-style links, fenced code blocks with language tags, tables and lists. Use when writing or editing any markdown file (README, AGENTS, docs, plans, skill files), or when adding a heading, link, table or code block. Owns markdown structure; pairs with prose-standard, which owns voice, grammar, spelling and punctuation.
tools
How to measure whether convention corrections keep recurring in the pi session logs, by category and by week. Use to record a baseline before the convention gates take effect and to re-run afterwards to confirm the recurring categories bend down. Pairs with the convention gates (pr-guardian, issue-guardian, commit-guardian, slack-integration) and the convention-context extension.