github

Standardizes GitHub CLI workflows for pull request triage, issue management, and CI/CD run analysis.

6|Updated May 18, 2026
One-click install
npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill github-mokhtarabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/mokhtarabadi/cognitive-lead-hq/tree/main/skill-templates/github
Command: npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill github-mokhtarabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub operations from the command line involves inconsistent commands, fragile shell escaping for issue bodies, and tedious CI failure debugging. This Skill provides a canonical standard operating procedure for all GitHub CLI (gh) workflows so agents and developers execute them consistently and safely. ## Core Features & Use Cases - Issue Management: List, view, and create issues with a mandatory --body-file pattern that prevents shell escaping and Markdown corruption. - Pull Request Triage: View PR details, diffs, checks, and comments using structured gh pr commands with --json and --jq output filtering. - CI/CD Debugging: Follow a four-step runbook to identify failing checks, locate run IDs, inspect failed jobs, and fetch failure logs. - Use Case: A pull request's CI check fails. Use this Skill to run gh pr checks, find the failing run with gh run list, and pull the exact error output with gh run view --log-failed to diagnose the root cause. ## Quick Start Ask the agent to check the status of pull request 55 and show the logs for any failing CI checks using the GitHub CLI workflow.

Frequently Asked Questions about github

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

FAQPage Schema
How do I debug a failing GitHub Actions CI check from the CLI?▼

Run gh pr checks to identify failing checks, then gh run list to find the run ID, gh run view to see failed jobs, and gh run view --log-failed to fetch detailed error output for the failing steps.

How to create a GitHub issue with a Markdown body using gh CLI?▼

Write the Markdown content to a temporary file with a heredoc, then pass it via gh issue create --body-file instead of inline --body. This avoids shell escaping errors and Markdown corruption, and the temp file should be deleted afterward.

Can I get structured JSON output from GitHub CLI commands?▼

Yes, most gh commands support --json with field names, filterable using --jq expressions. For data not exposed by subcommands, gh api provides direct access to the GitHub REST API with the same --jq filtering.

What GitHub operations are forbidden for autonomous agents?▼

Under the Zero-Autonomous-Commit policy, agents cannot run gh release create, git push, or git tag. These operations are denied at the permission layer and must be executed manually by the Manager after task closure.

What are the prerequisites for using the GitHub CLI workflow?▼

The gh CLI must be installed and authenticated before any operation. Verify with gh --version and gh auth status, and run gh auth login if authentication is missing.