start-work-loop

Automate issue resolution from scope selection to PR creation.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/eygraber/jellyfin-kmp --skill start-work-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-work-loop
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/start-work-loop
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill start-work-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Automates end-to-end issue work by selecting scope, implementing changes, and producing PRs, reducing manual coordination and idle time across a project.

Core Features & Use Cases

  • Auto-selects the next eligible issue within a defined scope (epics, labels, or readiness) and moves it into In Progress.
  • Implements a continuous work loop that reads scope, stacks branches to prevent conflicts, creates PRs, and updates issue statuses.
  • Unblocks dependent issues by recognizing blockers with PRs and advancing ready items; supports epic/subissue workflows for large initiatives.
  • Provides robust error handling and recovery mechanisms to continue in the face of non-fatal failures, while surfacing actionable details.

Quick Start

Start the loop for the defined scope and let it autonomously create PRs for ready issues.

Frequently Asked Questions about start-work-loop

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

FAQPage Schema
How do I automate GitHub issue resolution from discovery to pull request creation?

Automating GitHub issue resolution involves selecting eligible issues within epics, implementing changes, and creating PRs. This Skill autonomously progresses issues to PRs by moving scope from discovery through implementation, stacking branches to prevent conflicts, and updating issue statuses continuously.

What is the best way to handle dependent issues and blockers in an automated GitHub workflow?

Handling dependent issues in an automated GitHub workflow requires recognizing blockers with existing PRs and advancing ready items. This Skill unblocks dependent issues by applying dependency handling across multiple issues, supporting epic and subissue workflows for large initiatives.

Do I need gh and jq installed to automate issue tracking and pull request workflows?

Yes, you need the gh and jq command-line tools installed to automate issue tracking and pull request workflows. These dependencies are required for querying GitHub issues, managing branch stacking, and processing JSON outputs during the autonomous progression from ready issues to PRs.

Can I use automated branch stacking to prevent conflicts when creating multiple pull requests?

Automated branch stacking prevents conflicts when creating multiple pull requests by sequentially building branches. This Skill implements a continuous work loop that reads scope, stacks branches to avoid conflicts, and creates PRs for ready issues, ensuring autonomous progression without manual coordination.

How does error recovery work during autonomous issue progression and PR creation?

Error recovery during autonomous issue progression and PR creation handles non-fatal failures by continuing the work loop and surfacing actionable details. This Skill provides robust error handling and recovery mechanisms to ensure the automated workflow resumes without losing context or stopping unexpectedly.