issue-update

Update GitHub issues with comments, labels, and closing actions via gh CLI.

2|Updated Apr 6, 2017
One-click install
npx skills add https://github.com/shiiman/dotfiles --skill issue-update-shiiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-update
Source: https://github.com/shiiman/dotfiles/tree/main/ai/codex/skills/issue-update
Command: npx skills add https://github.com/shiiman/dotfiles --skill issue-update-shiiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates updating GitHub issues by applying comments, changing labels, and closing issues based on progress and user instructions.

Core Features & Use Cases

  • Update issue status automatically based on progress.
  • Add comments, adjust labels, and close issues.
  • Determine the target issue from user instructions (e.g., "update #5"), the current branch name (e.g., feature/5), or recent context.

Quick Start

Update the target GitHub issue by adding a summary comment, adjusting labels, and closing it when complete.

Frequently Asked Questions about issue-update

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

FAQPage Schema
How do I automate GitHub issue updates with comments and labels?

You can automate GitHub issue updates by using prompts like "update #5" to apply comments, adjust labels, and close issues. This process uses GitHub CLI operations to manage issue status based on progress.

Can I close a GitHub issue automatically from a branch name?

Yes, GitHub issue closures can be inferred automatically from branch context. By parsing issue numbers from branch names like "feature/5", the workflow triggers gh issue close operations without manual input.

Do I need GitHub CLI access to update issue status automatically?

Yes, GitHub CLI access is required to automate issue updates. The workflow relies on gh issue view, comment, edit, and close operations to apply labels, add comments, and close issues safely.

What is the best way to track development progress on GitHub issues?

The best way to track development progress on GitHub issues is by automating status updates. This workflow adds summary comments, adjusts labels, and closes issues based on user instructions and workflow context.

Are there safeguards when automating GitHub issue closures?

Yes, safeguards are included for safe updates when automating GitHub issue closures. The workflow parses target issues from user input or branch names and uses GitHub CLI operations to prevent unintended modifications.