skills.rest
tomzx
tomzxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gh-cached

Fetches GitHub issues, PRs, and comments with local caching.

5|Updated Jul 25, 2025
Search Tags:#caching#github#cli#issues#pull-requests#gh-cached
One-click install
npx skills add https://github.com/tomzx/agents --skill gh-cached
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-cached
Source: https://github.com/tomzx/agents/tree/main/skills/gh-cached
Command: npx skills add https://github.com/tomzx/agents --skill gh-cached

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-cached reduces repeated requests to GitHub by fetching issues, pull requests, and comments and caching results locally for fast, offline-friendly access.

Core Features & Use Cases

  • Fetch and view issues and PRs from a repository with cached results.
  • Minimise API calls by pre-populating the local cache.
  • Use with GitHub authentication to access private repos or higher rate limits.

Quick Start

Run gh-cached cache for a repository to pre-populate the local cache.

Frequently Asked Questions about gh-cached

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

FAQPage Schema
How do I cache GitHub issues and pull requests locally to reduce API calls?▼

You can cache GitHub issues and pull requests locally by running the gh-cached cache command for a repository. This pre-populates the local cache to minimize repeated API requests and improve browsing responsiveness.

Why does fetching GitHub issues repeatedly hit API rate limits?▼

Fetching GitHub issues repeatedly consumes API quota because requests are sent live each time. Using a local caching mechanism stores results under a cache directory, reducing API usage and preventing rate limit exhaustion during repository browsing.

Do I need a GitHub token to fetch and cache private repository PRs?▼

Yes, fetching and caching private repository pull requests requires a valid GH_TOKEN environment variable. Authentication allows access to private repos and provides higher API rate limits when pre-populating the local cache.

Can I browse cached GitHub issues offline?▼

Yes, you can browse cached GitHub issues offline once the local cache is populated. Fetching issues and pull requests stores results locally, enabling offline-friendly access without making new API calls to GitHub.

What is the best way to pre-populate a local cache for GitHub CLI queries?▼

The best way to pre-populate a local cache for GitHub queries is to run the gh-cached cache command for a specific repository. This fetches issues, PRs, and comments upfront, storing results locally for fast subsequent access.

Where are cached GitHub pull requests stored on my system?▼

Cached GitHub pull requests are stored locally under the ~/.cache/gh-cached/<host>/<owner>/<repo> directory. This structured path organizes cached repository data to improve query responsiveness and reduce API usage.

Related Skills

Explore More Software Engineering Skills→
MOODMNKY-LLCMOODMNKY-LLC

gh-issues

Convert GitHub issues into merged pull requests using the GitHub CLI.

Community
Advanced
OniroHuaverOniroHuaver
30

pr-comments

Fetch GitHub pull request comments from a repository branch using the GitHub API and gh CLI.

Community
Intermediate
jaredcroxtonjaredcroxton

github-code-review

Reviews local diffs and GitHub pull requests for critical issues.

Community
Intermediate
trailofbitstrailofbits
6.5k

gh-cli

Enforce authenticated gh CLI usage for GitHub repository operations.

Official
Basic