pick-issue

Select, prepare, and start software development issues from a Linear backlog.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill pick-issue-jamesc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pick-issue
Source: https://github.com/jamesc/skills/tree/main/skills/pick-issue
Command: npx skills add https://github.com/jamesc/skills --skill pick-issue-jamesc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of starting work on the next task from a backlog, ensuring a smooth transition into development.

Core Features & Use Cases

  • Automated Issue Selection: Identifies the next issue to work on based on explicit arguments, git worktree names, or backlog queries.
  • Pre-flight Checks: Validates issue state, checks for uncommitted changes, and ensures the working tree is clean before proceeding.
  • Branch Management: Creates feature branches automatically based on issue details.
  • Workflow Integration: Updates Linear, generates todo lists, and guides implementation with pattern lookups and testing.
  • Use Case: When you're ready for a new task, simply invoke /pick-issue and the Skill will handle finding the next item, setting up your branch, and updating your task status.

Quick Start

Use the pick-issue skill to start working on the next issue from the backlog.

Frequently Asked Questions about pick-issue

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

FAQPage Schema
How do I automate starting the next Linear issue from my backlog?

To automate starting the next Linear issue, you can use a workflow that identifies the task via explicit arguments or backlog queries, validates the current state, creates a git feature branch, and updates the Linear status.

How do I check for uncommitted changes before switching to a new git branch?

Checking for uncommitted changes before switching to a new git branch requires pre-flight validation to ensure the working tree is clean, preventing data loss and maintaining a smooth development workflow transition.

Can I use git worktree names to identify which issue to start?

Yes, you can use git worktree names to identify which issue to start, as the issue selection process supports identification through explicit arguments, worktree names, or direct Linear backlog queries.

What is the best way to manage git branching when picking up a new development task?

The best way to manage git branching for a new task is to automate feature branch creation based on issue details, ensuring the branch aligns with the specific development workflow and issue tracking context.

Does this issue tracking workflow update my Linear task status automatically?

Yes, the issue tracking workflow updates your Linear task status automatically as part of the workflow integration, transitioning the issue state and generating todo lists to guide implementation.

Why does starting a new issue require validating issue state and pre-flight checks?

Starting a new issue requires validating issue state and pre-flight checks to confirm the working tree is clean and the selected backlog item is ready, preventing conflicts and ensuring a smooth transition into development.