What does this skill do?

The GitHub Operations Skill manages the full cycle of repository maintenance operations using the gh CLI: issue triage, pull request management, CI/CD failure diagnosis, release publishing with auto-generated changelogs, and monitoring of Dependabot and secret scanning alerts. It ensures a consistent, traceable workflow that aligns with community best practices.

Issue Triage
Classify, tag, and respond to incidents. Detect duplicates by keyword and automatically request steps to reproduce the issue.
PR and CI Management
Check the status of CI checks, verify whether a PR is mergeable, and diagnose errors using detailed logs of the steps that failed.
Release Announcements
List of PRs merged since the last release, create versions with auto-generated notes, and prepare pre-release candidates.
Security Monitoring
Review Dependabot and secret scanning alerts, and list dependency PRs awaiting review.

Usage examples

🏷️ Issue triage
Search for duplicate issues related to "login error" and mark issue 42 as a high-priority bug.
🔀 IQ Assessment
Check the CI checks for PR 87 and show me the logs for the step that failed in the last run.
📦 New release
Create release v1.2.0 with release notes automatically generated from the pull requests merged since March.
🔒 Security Alerts
Check the Dependabot and secret scanning alerts for the repository and let me know which ones are active.

Features

Automated issue triage Duplicate detection, priority tagging, and guided comments to request information from reporters.
CI/CD Diagnostics List of failed executions, viewing logs for the problematic step, and selectively rerunning jobs.
Stale Policy Automatic flagging of inactive issues and PRs based on configurable thresholds, and traceable closure of obsolete items.
Releases with a changelog Generation of releases with automatically generated release notes and support for pre-release candidates.
Security Monitoring Review Dependabot and secret scanning alerts, and the list of pending dependency pull requests.

Frequently asked questions

Yes. The skill is based on the official GitHub CLI (gh). You must install it and authenticate with 'gh auth login' before using it.
Yes, as long as you have the appropriate permissions in the target repository (owner/repo) or are in the project directory.
Yes. By default, it marks issues as closed after 14 days of inactivity and PRs after 7 days, but you can adjust these thresholds to fit your workflow.
The skill returns gh commands ready to run, along with a summary of the repository's status. You decide when and how to run them.
GitHub Operations — Repository Management with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.