← ClaudeAtlas

github-projects-managerlisted

Execute GitHub Projects V2 operations — issue creation with automatic project board placement, custom field updates (single-select, text, number, date), batch field transitions, board queries, and board-hygiene audits (coverage: open issues not on the board; reconciliation: board Status vs the issue's real state/close-reason). Reads field schemas from workflow/projects/*.yaml configs. Works with gh CLI + GraphQL mutations. Trigger: "create issue", "set field", "update billing scope", "batch update approval", "board query", "add to project", "set status", "classify issue", "audit board", "board hygiene", "reconcile board", "orphan issues", "issues not on the board", "is everything on the board", "declined but not closed".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74
Install: claude install-skill bks-lab/open-bridge
# GitHub Projects Manager Execution layer for GitHub Projects V2 operations. The `project-advisor` skill handles governance and decision-making; this skill handles the actual CLI and GraphQL commands. ## When to use - Creating issues and adding them to project boards - Setting or updating custom project fields (Status, Priority, Billing Scope, Approval, Root Cause, Person Days, etc.) - Batch field transitions (e.g. "set Approval to Submitted on 16 items") - Querying board state (items by status, field counts, stale items) - Converting drafts to issues - **Auditing board hygiene** — coverage (open issues that never made it onto the board) and reconciliation (board Status disagreeing with the issue's real state / close-reason). See *Board Hygiene* below. ## Loading sequence 1. Identify the target project (from caller context, issue URL, or `#number`) 2. Read `workflow/projects/{slug}.yaml` for field values, governance rules, and state mappings 3. If a bound context exists (e.g. `workflow/contexts/customer-a.yaml`), read `project_custom_fields` for field-specific overrides and readonly field lists ## Issue Creation (3-step atomic) Every issue creation follows this exact sequence — no shortcuts: ``` Step 1: gh issue create --repo {org}/{issue_repo} --title --body --label Step 2: gh project item-add {number} --owner {org} --url {issue_url} Step 3: Verify — confirm the item appears on the board ``` After creation, immediately classify with at minimum: - `Sta