github-ops

Manage GitHub repository operations via the gh CLI.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill github-ops-mostafa-ismail-2004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-ops
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/github-ops
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill github-ops-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage GitHub repositories efficiently when you need to handle the operational work around issues, pull requests, releases, CI failures, and security alerts.

Core Features & Use Cases

  • Issue Triage: Classify, label, deduplicate, and respond to issues with consistent priorities and types.
  • PR Management: Check merge readiness, review activity, stale pull requests, and CI status.
  • CI/CD and Release Operations: Investigate failed workflows, rerun jobs, and prepare changelogs and releases.
  • Security Monitoring: Review Dependabot alerts, secret scanning findings, and dependency update PRs.
  • Use Case: A maintainer can quickly ask for help reviewing a failing PR, labeling a backlog issue, or preparing the next release.

Quick Start

Use the github-ops skill to triage open issues in my repository and label anything that looks like a bug or duplicate.

Frequently Asked Questions about github-ops

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

FAQPage Schema
How do I triage open GitHub issues and label duplicates automatically?

To triage GitHub issues, the Skill classifies, labels, and deduplicates open items using consistent priority rules. It reads repository issues via the authenticated gh CLI and applies appropriate labels based on issue content.

Can I check pull request merge readiness and CI status without leaving my coding environment?

Yes, you can check PR merge readiness, review activity, and CI status directly. The Skill inspects pull request states and queries workflow runs through the gh CLI to report stale PRs and failed checks.

How do I investigate failed GitHub Actions workflows and rerun jobs?

Investigating failed GitHub Actions workflows is done by querying workflow runs and inspecting CI failure logs. The Skill uses gh CLI to analyze the failed jobs and can trigger actions to rerun them.

Do I need the gh CLI installed to manage repository releases and security alerts?

Yes, the gh CLI with authenticated repository access is required. The Skill depends on it to read issues, inspect PR status, query workflow runs, and perform GitHub API actions for releases and security monitoring.

What is the best way to prepare a changelog and manage Dependabot security alerts?

The best way to prepare changelogs and manage Dependabot alerts is using the Skill's CI/CD and security monitoring features. It reviews Dependabot alerts, secret scanning findings, and dependency update PRs to maintain repository health.

Why does issue triage require authenticated GitHub repository access?

Authenticated GitHub repository access is required because the Skill performs GitHub API actions. It needs the gh CLI to read repository issues, inspect PR status, and query workflow runs for accurate triage and labeling.