file-e2e-panel

Files GitHub issues requesting e2e panel test runs and sweeps stale unclaimed panel issues.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill file-e2e-panel-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-e2e-panel
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/file-e2e-panel
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill file-e2e-panel-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end testing of the genealogy research loop depends on a fixed panel of four fixtures, but runs collapsed from 43 per week to 1 because a single operator did all the work. This Skill distributes that work by filing one unassigned half-day GitHub issue per fixture on every invocation, so the e2e corpus gets runs from multiple operators instead of one. ## Core Features & Use Cases - Batch issue filing: Creates four GitHub issues per run (one per fixed panel fixture) with the e2e-panel and genealogist labels, each containing a short run guide with the exact make commands and grading steps. - Panel status reporting: Runs make e2e-panel to report each fixture's last run date and trailing 28-day run count, surfacing when issues are filed but never staffed. - Stale issue sweep: Proposes closing panel issues older than 14 days that are unassigned and have no linked PR, checking linkage both via PR title/body search and closedByPullRequestsReferences. - Use Case: A project lead notices e2e coverage has stalled and says "file the e2e panel". The Skill verifies the label exists, files four fresh issues, reports the panel trend, and proposes closing two-week-old unclaimed issues — then waits for approval before applying anything. ## Quick Start Ask the assistant to file the e2e panel so four new genealogist run tasks are created and stale unclaimed panel issues are proposed for closing.

Frequently Asked Questions about file-e2e-panel

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

FAQPage Schema
How do I file e2e panel run issues on GitHub?▼

Invoke the skill with a phrase like "file the e2e panel". It verifies the e2e-panel label exists, then creates four issues with gh issue create — one per fixture — each labeled e2e-panel and genealogist with run instructions in the body.

How do I check e2e panel run coverage over time?▼

Run make e2e-panel to see each fixture's last run date, days since, and run count over the trailing 28 days. Use SINCE=all for full history, but the trailing month is the number that shows whether the panel is working.

Why does gh issue list with a missing label show empty results?▼

Querying issues by a nonexistent label exits 0 with empty output, which looks identical to a clean board. The skill checks the label with gh api first, because gh issue create with a missing label also fails without filing anything.

When are stale e2e panel issues closed?▼

Issues older than 14 days that are unassigned and have no linked PR are proposed for closing as "not planned". Linkage is checked two ways — PR title/body search and closedByPullRequestsReferences — because neither method alone catches all linked PRs.

Can the skill run the e2e tests itself?▼

No. The skill deliberately has no Edit or Write tools and never executes e2e runs; each filed issue is a half-day task for a human genealogist. It also never writes to the GitHub project board, which is handled automatically by add-to-project.yml.