address-issue

Convert GitHub issues into tusk tasks with acceptance criteria.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/gioe/python-libs --skill address-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: address-issue
Source: https://github.com/gioe/python-libs/tree/main/.claude/skills/address-issue
Command: npx skills add https://github.com/gioe/python-libs --skill address-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetching and prioritizing work from GitHub issues can be tedious; this skill automates turning an issue into a tusk task and kickstarts the full /tusk workflow.

Core Features & Use Cases

  • Parses an issue reference (number or URL) and derives a task summary, description, priority, and domain.
  • Fetches project config and backlog, analyzes labels and body to generate acceptance criteria and task fields.
  • Inserts a new tusk task and initiates the /tusk workflow, with optional follow-up actions on the related GitHub issue.

Quick Start

Provide a GitHub issue number or URL to convert that issue into a tusk task and begin the /tusk workflow.

Frequently Asked Questions about address-issue

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

FAQPage Schema
How do I convert a GitHub issue into an actionable task?

To convert a GitHub issue into an actionable task, provide the issue number or URL to parse its details, generate acceptance criteria, and insert a new task into your backlog management system.

Can I automate backlog management by turning GitHub issues into tusk tasks?

Yes, you can automate backlog management by parsing issue references, analyzing labels and body text, and automatically generating tusk tasks with derived priorities and domains.

Do I need the gh CLI to parse GitHub issues and generate acceptance criteria?

Yes, you need the gh CLI integration to fetch GitHub issue details, analyze project config backlogs, and generate acceptance criteria for cross-repo coordination.

What's the best way to handle issue triage and cross-repo coordination automatically?

The best way to handle issue triage and cross-repo coordination is automating issue extraction to generate task summaries, insert tusk tasks, and update issue status with optional follow-up actions.

How does issue triage work when creating tusk tasks from GitHub issues?

Issue triage works by fetching the project config and backlog, analyzing issue labels and body to derive a task summary, priority, and domain, then initiating the tusk workflow.