queue-run

Orchestrate sequential GitHub feature pipelines with agent subagents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/XiriGo/ecommerce-mobile --skill queue-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queue-run
Source: https://github.com/XiriGo/ecommerce-mobile/tree/main/.claude/skills/queue-run
Command: npx skills add https://github.com/XiriGo/ecommerce-mobile --skill queue-run

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the sequential processing of development features defined in GitHub Issues, ensuring a consistent and trackable pipeline from development to merge.

Core Features & Use Cases

  • Sequential Feature Processing: Runs the full agent pipeline for each feature in dependency order.
  • GitHub Integration: Tracks all actions (issues, PRs, project boards) directly within GitHub.
  • Dependency Management: Automatically resolves and respects feature dependencies before processing.
  • Use Case: Streamline the development workflow by automatically picking up the next ready feature from GitHub, building it, testing it, and creating a pull request, all without manual intervention.

Quick Start

Run the queue-run skill to process all ready features in dependency order.

Frequently Asked Questions about queue-run

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

FAQPage Schema
How do I automate feature development pipelines directly from GitHub Issues?

You can automate feature development from GitHub Issues by orchestrating a sequential pipeline that claims issues, creates branches, executes isolated tasks, runs quality gates, and opens auto-merging pull requests.

How does dependency resolution work when processing queued GitHub features?

Dependency resolution works by automatically identifying and respecting feature dependencies before processing, ensuring the pipeline only picks up ready features and builds them in the correct sequential order.

Can I use this to automatically create branches and pull requests without manual intervention?

Yes, you can automatically create branches and pull requests without manual intervention, as the pipeline manages branch creation, isolated pipeline execution, and post-merge cleanup directly on GitHub.

What is the best way to track CI/CD progress for issue tracking on GitHub?

The best way to track CI/CD progress is to use a GitHub-native pipeline that logs all actions, including issue claiming and pull request creation, directly onto your GitHub project boards.

Do I need to manually clean up branches after an automated pull request merges?

No, you do not need to manually clean up branches after a merge, because the pipeline handles post-merge cleanup automatically once the quality gates are passed and the pull request is merged.

When should I not use a sequential pipeline for GitHub issue tracking?

You should not use a sequential pipeline for GitHub issue tracking if your features lack clear dependency order or require parallel, non-isolated development outside of standard branch and pull request workflows.