work-issue

Fetches GitHub issue details and generates a branch name and implementation plan.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill work-issue-generaljerel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-issue
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/work-issue
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill work-issue-generaljerel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pick up a GitHub issue — fetches the issue details, creates a properly named branch, and sets up a context for implementation to accelerate start-of-work.

Core Features & Use Cases

  • Fetch issue details from GitHub to understand scope and ownership.
  • Create a branch named from the issue type (feat/fix/chore) and issue number for traceability.
  • Read local project context (chalk.json) when available to tailor file layout and commands.
  • Generate a structured to-do list and implementation plan that guides the work.

Quick Start

Use this skill by providing a GitHub issue number or URL to immediately prepare a branch and task plan.

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 intake and branch creation?

Automate GitHub issue intake by providing an issue number or URL to fetch issue details, derive a branch name from labels, and generate an implementation plan. This accelerates start-of-work by preparing the development context automatically.

Can I generate a branch name from GitHub issue labels automatically?

Yes, you can generate a branch name from GitHub issue labels automatically. The skill reads issue labels to derive standard branch prefixes like feat, fix, or chore combined with the issue number for full traceability.

How do I create an implementation plan from a GitHub issue?

Create an implementation plan from a GitHub issue by fetching issue details and parsing local project context. The skill outputs a structured to-do list that guides the development work based on the issue scope and local configurations.

Does this issue triage workflow work with local project configuration files?

Yes, the issue triage workflow works with local project configuration files. It parses local chalk.json context when available to tailor the file layout and commands to the specific software project conventions.

Do I need a specific repository convention to automate issue branching?

You need a typical software project using Chalk-like repo conventions to fully automate issue branching. The skill relies on these conventions to parse local context and accurately derive branch names from issue labels.

Why use an automated workflow for starting work on GitHub issues?

Use an automated workflow for starting GitHub issues to eliminate manual setup errors and accelerate development. It fetches details, creates a traceable branch, and sets up context immediately, ensuring a structured implementation plan is ready.