github-issue-ops

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.