bai-update

Automate Black Atom issue updates via GitHub CLI and GraphQL.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill bai-update
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: bai-update
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/bai-update
Command: npx skills add https://github.com/nikbrunner/dots --skill bai-update

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill requires gh, gh api, jq.

What problem does it solve?

Automates updating Black Atom issues by changing status, applying labels, adding comments, and managing related items to streamline project work.

Core Features & Use Cases

  • Update issue status (Todo β†’ In Progress β†’ In Review β†’ Done) across repos.
  • Add comments, set priorities, and link or create sub-issues and blockers.
  • Close issues and apply labels to reflect current state; supports cross-repo references using repo#number notation.

Quick Start

Provide an issue identifier and the desired update to apply, and the agent will perform the requested changes.

Frequently Asked Questions about bai-update

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

FAQPage Schema
How do I automate updating GitHub issue status transitions and labels across multiple repositories?β–Ό

Automating GitHub issue updates across repositories uses the GitHub CLI and GraphQL to change status, apply labels, and add comments. This Skill operates on repo#number inputs to manage project workflows and returns a summary of applied changes.

How do I add comments, set priorities, and link sub-issues to GitHub issues via the command line?β–Ό

Adding comments, setting priorities, and linking sub-issues via the command line is done by passing the repo#number identifier and the desired action to an automation tool. The tool leverages GitHub CLI and GraphQL to execute metadata changes and status transitions.

Do I need jq and GitHub CLI installed to automate project management issue updates?β–Ό

Yes, you need jq and the GitHub CLI (gh) installed to automate project management issue updates. The Skill relies on gh api and jq to execute GraphQL queries, load project constants, and map field option IDs for issue transitions.

What is the best way to manage blocked-by relationships and close issues across different GitHub project repos?β–Ό

The best way to manage blocked-by relationships and close issues across different GitHub project repos is using an automation Skill that supports cross-repo references via repo#number notation. It applies GraphQL updates to link blockers and close issues efficiently.

Why does the issue update automation require loading project constants from a specific configuration source?β–Ό

Loading project constants from a configuration source like about:bai is required because the automation needs to map field and option IDs for GitHub project status transitions. Without these mapped constants, the GraphQL API cannot accurately update issue metadata.