github

Automate GitHub issues, pull requests, and CI monitoring via the GitHub CLI.

67|24|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/openxjarvis/openclaw-python --skill github-openxjarvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/openxjarvis/openclaw-python/tree/main/skills/github
Command: npx skills add https://github.com/openxjarvis/openclaw-python --skill github-openxjarvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines interactions with GitHub repositories, automating common tasks related to issues, pull requests, and continuous integration runs, thereby reducing manual effort and improving development workflow efficiency.

Core Features & Use Cases

  • Issue Management: Create, list, and close GitHub issues.
  • Pull Request Operations: List, view, create, and merge pull requests.
  • CI/Workflow Monitoring: Check the status of CI runs, view logs, and re-run failed jobs.
  • API Queries: Fetch repository data, labels, and statistics using the GitHub API.
  • Use Case: When a pull request fails its CI checks, use this Skill to quickly view the logs and identify the cause of the failure.

Quick Start

Use the github skill to list all open pull requests for the repository owner/repo.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub issue tracking and pull request management from the command line?

You can automate GitHub issue tracking and pull request management by executing CLI commands to create, list, view, and close issues or PRs directly from your terminal, reducing manual repository navigation.

How do I check CI/CD pipeline status and view logs for a failed GitHub workflow run?

To check CI/CD pipeline status, you can inspect workflow run statuses and retrieve logs for failed jobs, allowing you to quickly identify the cause of continuous integration failures without opening a browser.

Do I need the GitHub CLI installed and authenticated to manage repository operations?

Yes, you need the GitHub CLI tool installed and authenticated on your local machine to execute commands for managing issues, pull requests, and monitoring CI/CD pipelines.

Can I fetch repository data and statistics using the GitHub API for automation scripts?

Yes, you can fetch repository data, labels, and statistics using GitHub API queries to integrate repository metrics into your automation scripts and development workflows.

What is the best way to merge pull requests and close related issues simultaneously?

The best way to merge pull requests and close issues is by using CLI commands to merge PRs and close the associated issues sequentially, streamlining your repository management workflow.

Why does my GitHub CI run fail to trigger and how can I re-run failed jobs?

If a GitHub CI run fails, you can inspect the workflow logs to identify the error and execute a command to directly re-run the failed jobs within the continuous integration pipeline.