What problem does it solve?
Maintainers of the Happier project receive GitHub issues that mix raw user reports, pre-diagnosed engineering claims, private diagnostics, and linked pull requests. This Skill establishes what is actually true about an issue bundle—root cause, affected versions, and justified response—before any fix or GitHub mutation happens.
Core Features & Use Cases
- Evidence-based diagnosis: Classifies reports, builds a minimal factual issue record, resolves private diagnostics through maintainer tooling, and traces the causal chain to the canonical code owner.
- Version and release provenance: Distinguishes reported, source, loaded, fix, and release bases so claims like "fixed" or "regression" are tied to named artifacts rather than assumptions.
- Linked PR assessment: Evaluates linked pull requests against the independently verified issue contract in read-only advisory mode, flagging partial, wrong-owner, or obsolete fixes.
- Use Case: A maintainer points the Skill at issue #210; it reproduces the defect on the reported release, identifies the owning component, confirms the fix exists on dev but not in any shipped artifact, and proposes a
stage:source label plus a reporter-facing comment.
Quick Start
Use the happier-issue-diagnose skill to investigate GitHub issue #123 and tell me the verified root cause, affected versions, and recommended response.
