work-issue

Orchestrate GitHub issue workflows from fetching details to reporting results.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/shwilliamson/a-test --skill work-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-issue
Source: https://github.com/shwilliamson/a-test/tree/main/.automatasaurus/skills/work-issue
Command: npx skills add https://github.com/shwilliamson/a-test --skill work-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, automated workflow to work on a single GitHub issue using dedicated commands, ensuring consistent behavior across agents and executions.

Core Features & Use Cases

  • Orchestrates per-issue work across /work and /work-all commands to ensure a unified approach.
  • Enforces a deterministic workflow: fetch issue details, check dependencies, gather design specs, implement changes, coordinate reviews, handle feedback, and report outcomes.
  • Uses the GitHub CLI to retrieve issue and pull request information and drive automated actions for issue-driven development.
  • Use Case: When starting work on issue #123, the skill coordinates all steps and surfaces final status for merge readiness.

Quick Start

Provide an ISSUE_NUMBER to the orchestrator to begin processing a specific GitHub issue, for example by invoking the work-issue skill with ISSUE_NUMBER set to your target issue.

Frequently Asked Questions about work-issue

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

FAQPage Schema
How do I automate GitHub issue work with an agent?

Automating GitHub issue work involves orchestrating a deterministic workflow that fetches issue details, checks dependencies, implements changes, and coordinates reviews. This skill uses the GitHub CLI to drive that structured, repeatable agent process end-to-end.

What is an automated workflow for issue-driven development?

An automated workflow for issue-driven development standardizes per-issue tasks from fetching details to reporting outcomes. It enforces consistent behavior across agents by coordinating implementation, reviews, and feedback handling for any GitHub issue.

Do I need the GitHub CLI to orchestrate issue work?

Yes, you need the GitHub CLI installed and authenticated. The skill relies on the GitHub CLI to retrieve issue and pull request information and to drive automated actions for issue-driven development.

Can I process multiple GitHub issues automatically?

Yes, you can process multiple GitHub issues automatically. The skill orchestrates per-issue work across the /work and /work-all commands, ensuring a unified approach for coordinating all steps and surfacing final status.

What's the best way to standardize agent behavior for GitHub issues?

The best way to standardize agent behavior for GitHub issues is to enforce a deterministic workflow. This approach fetches details, gathers design specs, implements changes, handles feedback, and reports outcomes consistently across executions.

Why does my automated GitHub issue workflow need design specs?

Automated GitHub issue workflows need design specs to gather implementation requirements before coding. Checking dependencies and gathering specs ensures the agent coordinates changes accurately and surfaces correct final status for merge readiness.