github-ops

Automates GitHub issue triage, PR management, CI debugging, and releases using the gh CLI.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill github-ops-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-ops
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/github-ops
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill github-ops-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a healthy GitHub repository requires constant manual effort: triaging incoming issues, tracking stale PRs, debugging CI failures, preparing releases, and monitoring security alerts. This Skill automates those operational workflows through the gh CLI so repository maintenance stays consistent and nothing falls through the cracks. ## Core Features & Use Cases - Issue Triage: Classify issues by type and priority, detect duplicates, apply labels, and draft responses automatically. - PR & CI Management: Check review status, mergeability, and CI failures, then diagnose flaky tests versus real breakage. - Release & Security Operations: Generate changelogs from merged PRs, create releases, and monitor Dependabot and secret-scanning alerts. - Use Case: A maintainer returns after a week away and asks the agent to triage all new issues, flag PRs older than 7 days without review, and confirm CI is green before cutting a release. ## Quick Start Ask the agent to triage all open issues in this repository, label them by type and priority, and report any PRs that have been waiting more than 7 days for review.

Frequently Asked Questions about github-ops

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

FAQPage Schema
How do I triage GitHub issues automatically with the gh CLI?▼

Use gh issue list with search filters to find duplicates, then gh issue edit --add-label to classify by type and priority, and gh issue comment to post responses. The Skill follows a workflow covering bugs, feature requests, questions, and good first issues.

How to debug a failing GitHub Actions CI workflow?▼

Run gh run list --status failure to find failed runs, then gh run view <run-id> --log-failed to inspect the failing step. Distinguish flaky tests from real failures before re-running with gh run rerun --failed.

What do I need to use this GitHub operations Skill?▼

You need the GitHub CLI (gh) installed and authenticated via gh auth login with access to the target repository. All operations, including issues, PRs, releases, and security alerts, run through gh commands and the GitHub API.

Can I manage stale issues and PRs on GitHub automatically?▼

Yes. The Skill applies a stale policy: issues inactive for 14+ days get a stale label and comment, PRs inactive for 7+ days get a follow-up comment, and stale issues auto-close after 30 days with a closed-stale label.

Does the gh CLI support Dependabot and secret scanning alerts?▼

Yes, via gh api endpoints such as repos/{owner}/{repo}/dependabot/alerts and secret-scanning/alerts. The Skill flags critical and high severity alerts immediately and recommends reviewing dependency bump PRs weekly.