What problem does it solve?
Fixing confirmed GitHub issues or review blockers in the Comet repository requires careful boundary control: protecting the user's current checkout, choosing the correct Native or Classic workflow, running risk-matched tests, and avoiding unauthorized commits or PRs. This Skill enforces that disciplined process.
Core Features & Use Cases
- Boundary Confirmation: Verifies the reported issue actually exists, checks branch state and dirty files, and isolates work in a separate worktree when needed.
- Workflow-Aligned Implementation: Routes changes through the appropriate Native or Classic workflow, manages Runtime state and generated assets via supported commands, and keeps changes minimal.
- Verification and Handoff: Runs minimal relevant tests first, escalates to build/lint/full checks when crossing boundaries, and hands off to comet-safe-delivery only with user authorization.
- Use Case: A maintainer confirms a validated GitHub issue on Comet, implements the minimal fix with a focused regression test in an isolated worktree, runs targeted tests, and reports local versus CI results without committing.
Quick Start
Use the comet-github-issue-fix skill to safely implement the verified fix for this confirmed Comet GitHub issue.