skills.rest
OpenKnots
OpenKnotsOFFICIAL
Explore all skills by this author →
Website𝕏@openknotGitHub

github

Fetch current GitHub repository, pull request, issue, and CI check states.

23|13|Updated Mar 25, 2026
Search Tags:#github#repository#issues#pr#code-review#ci
One-click install
npx skills add https://github.com/OpenKnots/okcode --skill github-openknots
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/OpenKnots/okcode/tree/main/packages/shared/src/skills-catalog/recommended/github
Command: npx skills add https://github.com/OpenKnots/okcode --skill github-openknots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to inspect GitHub repositories, pull requests, issues, and CI workflows to ground decisions in live data rather than memory.

Core Features & Use Cases

  • Real-time repository context: fetches current state across PRs, issues, checks, and branches to support review and triage.
  • Actionable guidance: ties findings to exact PR numbers, file paths, and check names for precise follow-ups.
  • Use Case: during a code review, pull the latest build status and failing tests to prioritize fixes.

Quick Start

Run an initial repo scan to surface open PRs and recent CI results.

Frequently Asked Questions about github

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

FAQPage Schema
How do I get real-time repository context for code review and triage?▼

Real-time repository context is obtained by using GitHub APIs or adapters to fetch current pull requests, issues, and CI workflow checks. This grounds code review and triage decisions in live data rather than memory, tying findings to exact PR numbers and file paths.

What is the best way to check pull request and CI status before a release?▼

The best way to check pull request and CI status is running a repository scan to surface open PRs and recent workflow checks. This fetches live GitHub metadata to assess release readiness, identifying failing tests and build statuses for precise follow-ups.

Do I need scoped permissions to fetch GitHub issues and workflow checks?▼

Yes, you need proper authentication and scoped permissions to fetch GitHub issues and workflow checks. Configuring these access credentials allows the API adapters to securely retrieve repository metadata, pull requests, and CI results for your triage sessions.

How does fetching live GitHub metadata improve release readiness?▼

Fetching live GitHub metadata improves release readiness by identifying the current state across repositories, pull requests, issues, and CI checks. Up-to-date metadata informs actions, allowing teams to prioritize fixes based on exact failing test names and build statuses.

Can I use this to surface failing CI checks across multiple pull requests?▼

Yes, you can surface failing CI checks across multiple pull requests by querying GitHub APIs for workflow results. This identifies current build statuses and failing tests, tying them to exact PR numbers and check names to support prioritized code fixes.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
przbaduprzbadu
1

pr-review

Review GitHub pull requests and fix Copilot comments using parallel agents.

Community
Advanced
OrestesKOrestesK
2

iterate-pr

Diagnose GitHub pull request failures, apply validated fixes, and monitor checks.

Community
Advanced
letta-ailetta-ai
327

github

Automate GitHub issues, PRs, and workflow inspections via the gh CLI.

Official
Intermediate