Individual skill

evo-gh-data-fetcher

Fetches pull request and issue data from a GitHub repository using the GitHub REST API via curl/subprocess. Handles JSON output parsing, pagination, date range filtering, and error handling. Use when you need to retrieve structured PR or issue data from GitHub for analysis.

tasks-evolved/gh-repo-analytics/environment/skills/evo-gh-data-fetcher/SKILL.md

Read pinned source

Source commit 84ca182da055fafb6453dcec4a6defdbbfd987c1

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 97
Repository last updated: Sep 10, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
llm-agents Repository topic
open-world Repository topic
self-evolving-agents Repository topic
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,623 bytes
SKILL.mdcore · 2,623 bytes
scripts/fetch.pyruns · 5,081 bytes
scripts/utils.pyruns · 4,269 bytes

Read excerpt


# evo-gh-data-fetcher

Fetches PR and issue data from GitHub repositories using the GitHub REST API (via curl subprocess calls). Works without gh CLI authentication by using unauthenticated API access for public repos.

## Key Concepts

- Uses GitHub Search API (`/search/issues`) with query qualifiers like `type:pr`, `type:issue`, `created:YYYY-MM-DD..YYYY-MM-DD`
- Search API returns max 1000 results per query; pagination handled automatically
- PR details (merge status, merged_at) require individual PR endpoint calls (`/repos/{owner}/{repo}/pulls/{number}`)
- Timestamps are ISO 8601 format with Z suffix (e.g., `2024-12-15T10:30:00Z`)
[Credential-related source omitted]
- PR states from API: `open`, `closed` with `merged` boolean and `merged_at` timestamp
- Issue labels are returned as array of objects: `[{"name": "bug", ...}]`