skills.rest
ProxiBlue
ProxiBlueCOMMUNITY
Explore all skills by this author →
Website𝕏@proxiblueGitHub

github-analysis

Reproduce GitHub issues locally by substituting URLs and syncing data.

15|1|Updated Oct 24, 2025
Search Tags:#github#ddev#issue-analysis#local-reproduction#database-sync#media-download
One-click install
npx skills add https://github.com/ProxiBlue/claude-skills --skill github-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-analysis
Source: https://github.com/ProxiBlue/claude-skills/tree/main/github-analysis
Command: npx skills add https://github.com/ProxiBlue/claude-skills --skill github-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures GitHub issues are reproduced locally in a deterministic environment before proposing solutions, reducing wasted effort due to cache, data, or configuration differences.

Core Features & Use Cases

  • Local reproduction workflow: Read a ticket, replace production URLs with local DDEV hosts, and verify a faithful reproduction.
  • Environment validation and data sync: Validate that the local environment is running, pull fresh databases and media as needed, and re-run steps to confirm results.
  • Issue investigation documentation: Reproduce, document findings, and produce a structured report of root cause and fixes.

Quick Start

Provide a GitHub issue URL or number and run the skill to start a local reproduction workflow that converts prod URLs to local, starts services, and documents outcomes.

Frequently Asked Questions about github-analysis

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

FAQPage Schema
How do I reproduce GitHub issues locally before attempting a fix?▼

Local issue reproduction involves replacing production URLs with local DDEV hosts, validating services, syncing fresh databases and media, and documenting the outcomes to ensure environment parity before debugging.

Why does my local environment fail to reproduce a production GitHub issue?▼

Local reproduction fails when there are cache, data, or configuration differences between environments. Pulling fresh databases and media, alongside service validation, ensures faithful parity to reproduce the issue deterministically.

How do I use DDEV to sync databases and media for issue triage?▼

Using DDEV for issue triage requires validating that the local environment is running, then pulling fresh databases and media as needed to match production data and achieve faithful local reproduction.

What's the best way to document GitHub issue investigation findings?▼

The best way to document issue investigation is to reproduce the issue locally, record the findings, and produce a structured report detailing the root cause and proposed fixes for the GitHub ticket.

Can I use local reproduction workflows for both GitHub issues and pull requests?▼

Yes, local reproduction workflows apply to debugging and triage across both GitHub issues and pull requests, converting production URLs to local hosts and validating the environment to confirm results deterministically.

Related Skills

Explore More Software Engineering Skills→
muskie9muskie9

ddev-sync

Automate DDEV project synchronization with remote production database and assets.

Community
Intermediate
thisisryanswiftthisisryanswift
2

ce-debug

Diagnoses bugs via a five-phase workflow from trigger to symptom.

Community
Advanced
sjinkssjinks

triage-with-wpscan-vulnerability-testbench

Verify WPScan-reported vulnerabilities against a local DDEV test bench.

Community
Advanced
grasmashgrasmash
73

drupal-config-mgmt

Inspect Drupal config differences with read-only drush commands and --no flags.

Community
Intermediate