What problem does it solve?
Triaging and fixing Slate or Slate v2 GitHub issues manually requires reproducing bugs, verifying fixes against current source, and writing accurate issue comments, which is slow and error-prone.
Core Features & Use Cases
- Issue Intake and Classification: Fetches the issue via the GitHub CLI, extracts the user flow, expected and actual behavior, and classifies the state as red-current, already-accounted, needs-manual-proof, or blocked.
- Proof-Driven Fixing: Adds the smallest failing test or Playwright row, fixes the durable owner in the Slate v2 source, and runs focused verification commands.
- Verified Issue Comments: Posts a structured confidence-rated comment with gh and closes the issue only when verification reaches 95% or higher confidence.
- Use Case: A maintainer receives a Slate editor bug report with a screen recording; the Skill transcribes the video, reproduces the flow against current source, fixes the owning package, and posts a verified comment.
Quick Start
Resolve Slate issue number 123 from the udecode/slate repository and post the verified result as an issue comment.