GitHub Copilot Coding Agent automation. Apply the ai-copilot label to an issue → GitHub Actions auto-assigns Copilot via GraphQL → Copilot creates a Draft PR. One-click issue-to-PR pipeline.
Install with Tessl CLI
npx tessl i github:supercent-io/skills-template --skill copilot-coding-agent88
Quality
83%
Does it follow best practices?
Impact
96%
4.00xAverage score across 3 eval scenarios
If you add the
ai-copilotlabel to an issue, GitHub Actions automatically assigns it to Copilot, and Copilot creates a branch → writes code → opens a Draft PR.
repo scope# One-click setup (register token + deploy workflow + create label)
bash scripts/copilot-setup-workflow.shThis script does:
COPILOT_ASSIGN_TOKEN as a repo secret.github/workflows/assign-to-copilot.ymlai-copilot label# Create issue + ai-copilot label → auto-assign Copilot
gh issue create \
--label ai-copilot \
--title "Add user authentication" \
--body "Implement JWT-based auth with refresh tokens. Include login, logout, refresh endpoints."# Add label to issue #42 → trigger Actions
gh issue edit 42 --add-label ai-copilotexport COPILOT_ASSIGN_TOKEN=<your-pat>
bash scripts/copilot-assign-issue.sh 42Issue created/labeled
↓
GitHub Actions triggered (assign-to-copilot.yml)
↓
Look up Copilot bot ID via GraphQL
↓
replaceActorsForAssignable → set Copilot as assignee
↓
Copilot Coding Agent starts processing the issue
↓
Create branch → write code → open Draft PR
↓
Auto-assign you as PR reviewerRequired GraphQL header:
GraphQL-Features: issues_copilot_assignment_api_support,coding_agent_model_selection| Workflow | Trigger | Purpose |
|---|---|---|
assign-to-copilot.yml | Issue labeled ai-copilot | Auto-assign to Copilot |
copilot-pr-ci.yml | PR open/update | Run CI (build + tests) |
Copilot is treated like an external contributor.
copilot-pr-ci.yml CI runs normally# Check CI after manual approval
gh pr list --search 'head:copilot/'
gh pr view <pr-number>Review the issue spec in planno before assigning to Copilot (independent skill, not required):
Review and approve this issue spec in plannoAfter approval, add the ai-copilot label → trigger Actions.
PM writes an issue → add ai-copilot label
→ Actions auto-assigns → Copilot creates Draft PR
→ Team only performs PR reviewFollow-up issues created by Vibe Kanban:
refactors/docs cleanup/add tests
→ ai-copilot label → Copilot handles
→ Team focuses on main feature developmentJira issue → Zapier/webhook → auto-create GitHub Issue
→ ai-copilot label → Copilot PR
→ Fully automated pipeline# Bulk-add label to backlog issues
gh issue list --label "tech-debt" --json number \
| jq '.[].number' \
| xargs -I{} gh issue edit {} --add-label ai-copilot# List PRs created by Copilot
gh pr list --search 'head:copilot/'
# Specific issue status
gh issue view 42
# PR CI status
gh pr checks <pr-number>=== Setup ===
bash scripts/copilot-setup-workflow.sh one-time setup
=== Issue assignment ===
gh issue create --label ai-copilot ... new issue + auto-assign
gh issue edit <num> --add-label ai-copilot existing issue
bash scripts/copilot-assign-issue.sh <num> manual assign
=== Verify results ===
gh pr list --search 'head:copilot/' Copilot PR list
gh pr view <num> PR details
gh pr checks <num> CI status
=== Constraints ===
Copilot Pro+/Business/Enterprise required
First PR requires manual approval (treated as an external contributor)
PAT: repo scope required2311988
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.