GitHub CLI Workflows
Manage GitHub issues, PRs, and Actions workflows directly via the GitHub CLI.
$5
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsGitHub CLI Workflows
Example session with this skill installed
Check the CI status for PR #124 and show me the logs for any failed steps.
- Read your context and instructions
- Compiled the github cli workflows
I have checked the status of PR #124. The CI pipeline has failed on the 'Unit Tests' job.
CI Failure Analysis for PR #124
| Check Name | Status | Conclusion | URL |
|---|---|---|---|
| lint-and-format | completed | success | https://github.com/org/repo/runs/8821 |
| unit-tests (node 18) | completed | failure | https://github.com/org/repo/runs/8822 |
| build-dist | completed | skipped | https://github.com/org/repo/runs/8823 |
Failed Log Output (unit-tests)
> test:unit
> jest
FAIL src/auth/service.spec.ts
● AuthService › should validate JWT secret
expect(received).toBe(expected) // Object.is equality
Expected: true
Received: false
14 | it('should validate JWT secret', () => {
> 15 | expect(service.validate(mockSecret)).toBe(true);
| ^
16 | });
Next steps
- Review the logic in
src/auth/service.tsto ensure the secret validation matches the test expectation. - Run
npm testlocally to verify the fix. - Push changes to re-trigger the
unit-testsworkflow.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Managing GitHub issues, PRs, and CI workflows requires constant context switching between the terminal and the browser. Querying specific pull request metadata or debugging failed CI logs manually is slow and breaks development flow.
What it does
- Interrogates GitHub PRs for CI check statuses and specific metadata fields.
- Retrieves and filters recent GitHub Action workflow runs.
- Extracts logs for failed pipeline steps to speed up debugging.
- Executes advanced data queries using JSON output and JQ filtering.
- Manages issues and pull requests directly through the
ghCLI interface.
Frameworks & tools
GitHub CLI (gh), GitHub Actions, JQ.
Why this beats prompting it yourself
Generic LLMs often hallucinate CLI flags or mix up git and gh syntax. This skill provides precise, tested command patterns for structured JSON extraction and log retrieval, ensuring the agent interacts with your repository's state accurately without manual command lookups.
Use cases
- Identify why a PR pipeline failed by pulling specific error logs.
- List and filter open issues based on custom labels or authors.
- Monitor the status of multiple concurrent GitHub Action runs.
- Fetch PR metadata for automated changelog or report generation.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 25 days ago
- Passed all security checks, Safe to install