comet-github-issue-fix

Implements verified GitHub issue fixes through isolated Comet workflows with scoped testing and delivery.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-github-issue-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-github-issue-fix
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-github-issue-fix
Command: npx skills add https://github.com/rpamis/comet --skill comet-github-issue-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about comet-github-issue-fix

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

FAQPage Schema
How do I safely fix a confirmed GitHub issue in the Comet repository?

Verify the issue exists in the live tracker, confirm branch and worktree state, then implement the minimal fix through the appropriate Native or Classic workflow. Run focused regression tests first and escalate to broader checks only when crossing boundaries.

What is the difference between Native and Classic workflows in Comet?

Native work uses the Native workflow while Classic work uses the Classic workflow; the skill routes implementation through whichever owns the task. If scope expands mid-implementation, you return to that workflow's Build or scope-confirmation step before adding files.

Does this skill commit or create pull requests automatically?

No. It never commits, pushes, comments, or opens PRs unless the user explicitly authorizes it. After authorization, it hands the exact file scope to the comet-safe-delivery skill.

When should I use an isolated worktree for an issue fix?

Use an isolated worktree or branch when the target branch or current workspace has uncommitted changes. This protects the user's existing checkout from interference during the fix.

Should internal issues found during feature development get a Changelog entry?

No. The skill only adds Changelog entries for user-visible behavior changes. Internal problems discovered while developing a new feature are fixed without a Changelog entry.