verify-timeline-event-coverage

Compare GitHub GraphQL schema with gh-timeline dispatcher expectations and apply patches.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/sushichan044/gh-timeline --skill verify-timeline-event-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-timeline-event-coverage
Source: https://github.com/sushichan044/gh-timeline/tree/main/.claude/skills/verify-timeline-event-coverage
Command: npx skills add https://github.com/sushichan044/gh-timeline --skill verify-timeline-event-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps identify discrepancies between GitHub's GraphQL schema and the gh-timeline dispatcher's expectations, ensuring the gh-timeline tool's correct functioning after a schema update.

Core Features & Use Cases

  • Schema Diff: Compare GitHub's schema against the gh-timeline's declarations.
  • Code Triage: Determine how to handle new events or deprecated fields.
  • Code Patching: Add new event handling code, update tests, and apply patches.
  • Live Verification: Test patches on live data to confirm functionality.
  • Optional Fixture Refresh: Update fixtures to include new events if required.
  • Use Case: After a GitHub schema update, use this skill to audit the gh-timeline tool and apply necessary patches before release.

Quick Start

Run the 'verify-timeline-event-coverage' skill to audit and apply necessary patches to gh-timeline for GitHub schema updates.

Frequently Asked Questions about verify-timeline-event-coverage

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

FAQPage Schema
How do I verify GitHub timeline event coverage after a GraphQL schema update?

To verify GitHub timeline event coverage post-schema update, compare the updated GitHub GraphQL schema against the gh-timeline dispatcher's expectations to identify discrepancies and apply necessary code patches.

How do I patch the gh-timeline dispatcher when GitHub schema updates introduce new events?

Patching the gh-timeline dispatcher requires comparing the new GitHub schema declarations, determining how to handle new events or deprecated fields, adding event handling code, and updating tests to apply the necessary patches.

Do I need a GitHub API connection to audit gh-timeline schema discrepancies?

Yes, auditing gh-timeline schema discrepancies requires an active GitHub API connection to fetch the latest schema and perform live verification of the applied patches against real timeline data.

What's the best way to handle deprecated fields in a gh-timeline dispatcher fallback?

The best way to handle deprecated fields in a gh-timeline dispatcher fallback is to perform a schema diff against GitHub's schema, triage the deprecated fields, and patch the dispatcher expectations accordingly.

Can I update gh-timeline test fixtures when verifying new GitHub timeline events?

Yes, you can optionally refresh and update test fixtures to include new GitHub timeline events, ensuring the gh-timeline dispatcher maintains complete event coverage and correct functionality during live verification.

Why does the gh-timeline dispatcher fail after GitHub GraphQL schema updates?

The gh-timeline dispatcher fails after GitHub GraphQL schema updates due to discrepancies between the updated schema and the dispatcher's expected event declarations, requiring a schema diff and code patching to restore functionality.