copilot-orchestration

Dispatch coding tasks to GitHub Copilot and verify pull requests in throwaway clones.

7|23|Updated Aug 9, 2015
One-click install
npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill copilot-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-orchestration
Source: https://github.com/gamedevpl/www.gamedev.pl/tree/main/.claude/skills/copilot-orchestration
Command: npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill copilot-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers safely delegate well-specified coding tasks to GitHub Copilot's remote coding agent while avoiding unsuitable work, incorrect branches, unverified changes, and unreliable completion signals.

Core Features & Use Cases

  • Remote Task Dispatch: Start and manage Copilot coding sessions through the Agent tasks REST API or issue assignment workflow.
  • Workflow Guidance: Specify task scope, base branches, models, custom agents, authentication requirements, and follow-up sessions.
  • Independent Verification: Poll task status, inspect artifacts and transcripts, validate changes in a throwaway clone, run tests, review diffs, and merge verified pull requests.
  • Use Case: Delegate a self-contained feature with a reliable test suite, verify the returned branch independently, and merge it only after confirming the scope and acceptance criteria.

Quick Start

Use the copilot-orchestration skill to dispatch a well-specified coding task to GitHub Copilot, monitor its progress, independently verify the resulting pull request in a throwaway clone, and merge it when the tests and review pass.

Frequently Asked Questions about copilot-orchestration

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

FAQPage Schema
How do I delegate coding tasks to GitHub Copilot's remote coding agent?

You can delegate coding tasks to GitHub Copilot's remote agent by dispatching well-specified instructions through the Agent tasks REST API or issue assignment workflow, configuring explicit base branches, task scope, and required authentication.

How do I independently verify changes from a Copilot coding agent before merging?

Verify Copilot agent changes by polling task status, inspecting artifacts and transcripts, validating modifications in a throwaway clone, running tests, reviewing diffs, and making security-conscious merge decisions on the pull request.

What is the best way to manage branch configuration for automated Copilot coding sessions?

Managing branch configuration for Copilot coding sessions requires specifying explicit base branches, task scope, models, and custom agents before dispatching the remote task to ensure correct targeting and reliable pull request verification.

Can I use GitHub Copilot remote coding agent for follow-up coding rounds on an existing pull request?

Yes, you can dispatch follow-up coding rounds to GitHub Copilot's remote agent by issuing new scripted Agent tasks API dispatches or issue-based assignments targeting the existing branch and updated task scope.

When should I avoid delegating work to a remote coding agent?

You should avoid delegating unsuitable work, insufficiently specified tasks, or changes lacking a reliable test suite to a remote coding agent, as independent verification and security-conscious merge decisions require clear scope and acceptance criteria.