github-issue-ops

Automate GitHub issue creation, viewing, updating, labeling, assignment, and closure via the gh CLI.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/faccomichele/open-claw-team --skill github-issue-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-ops
Source: https://github.com/faccomichele/open-claw-team/tree/main/skills/github-issue-ops
Command: npx skills add https://github.com/faccomichele/open-claw-team --skill github-issue-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating, updating, and tracking GitHub issues across a hybrid team of local OpenClaw agents and GitHub Copilot agents is time-consuming and prone to inconsistent labeling, missing context, and misassignment. This skill eliminates that friction by automating all common GitHub issue operations via the gh CLI.

Core Features & Use Cases

  • Full Issue Lifecycle Automation: Create, view, update, label, assign, and close GitHub issues without manual CLI input.
  • Seamless Copilot Integration: Assign issues directly to @copilot or custom Copilot agents (e.g., dev-backend, test-specialist) to kick off code tasks automatically.
  • Standardized Team Coordination: Enforce consistent labeling (owner, type, status) and agent-prefixed comments to keep issue tracking aligned across all team members and agents.
  • Use Case: A PM agent can use this skill to triage a new user-reported bug, add the correct owner and type labels, assign it to the dev-backend Copilot agent, and post a comment linking to the error log and related user feedback.

Quick Start

Use the github-issue-ops skill to create a new feature request issue for the open-claw-team repo, assign it to the dev-frontend Copilot agent, add the labels owner:tech-lead, type:feature, and post a comment linking to the relevant design mockup.

Frequently Asked Questions about github-issue-ops

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

FAQPage Schema
How do I automate GitHub issue creation and assignment using gh CLI?

You can automate GitHub issue management via gh CLI by creating, viewing, updating, labeling, assigning, and closing issues programmatically. This standardizes task tracking and delegation between OpenClaw agents and GitHub Copilot agents without manual CLI input.

Can I assign GitHub issues to Copilot agents for automated code execution?

Yes, you can assign GitHub issues to Copilot agents for automated code execution. The skill supports direct assignment to @copilot or custom agents like dev-backend and test-specialist to automatically kick off code tasks.

What is the best way to enforce consistent labeling across a multi-agent GitHub workflow?

The best way to enforce consistent labeling across a multi-agent GitHub workflow is to automate label application for owner, type, and status categories. This ensures issue tracking remains aligned across all team members and agents.

How do I track issue status in a hybrid team with local agents and Copilot agents?

You track issue status in a hybrid team by using agent-prefixed comments and standardized labels for cross-team communication. This keeps issue tracking aligned between local OpenClaw agents and GitHub Copilot agents throughout the issue lifecycle.

Do I need to install any additional dependencies to automate issue lifecycle operations with gh CLI?

No additional dependencies are required to automate issue lifecycle operations with gh CLI. The skill operates without external dependencies to manage the full lifecycle of GitHub issues including creation, updates, labeling, assignment, and closure.