flag-compiler-bug

Minimize compiler bug reproductions and file GitHub issue reports.

92|7|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dannys-code-corner/incan --skill flag-compiler-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flag-compiler-bug
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/flag-compiler-bug
Command: npx skills add https://github.com/dannys-code-corner/incan --skill flag-compiler-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.

Core Features & Use Cases

  • Verify observations of compiler defects and capture exact repro steps.
  • Minimize reproductions to the smallest honest repro.
  • Check for duplicates and link existing issues when relevant.
  • Draft and raise a bug report with a clean, sanitized template using create-github-issue.
  • Resume work only after a workaround is validated.

Quick Start

Observe a likely compiler bug, pause the task, and file a minimal reproducible bug report via the repository's issue workflow.

Frequently Asked Questions about flag-compiler-bug

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

FAQPage Schema
How do I report a compiler bug on GitHub with a minimal reproduction?▼

A compiler bug report requires pausing your task, minimizing the reproduction to the smallest honest test case, checking for duplicate issues, and drafting a sanitized bug report using create-github-issue to file the defect.

When should I stop working to triage a compiler defect?▼

Pause and triage a compiler defect when you encounter an ICE, panic, miscompile, wrong accept/reject behavior, or diagnostic bug during implementation, testing, or review work.

What is the best way to check for duplicate compiler issues before reporting?▼

Check for duplicate compiler issues by searching existing GitHub issues in the repository, linking relevant existing reports instead of filing a new bug when the defect is already documented.

Do I need to validate a workaround before resuming work after a compiler bug?▼

Yes, you must validate a workaround before resuming your task after a compiler bug, ensuring the defect does not block implementation and the alternative approach functions correctly.

What types of compiler defects should be minimized and reported?▼

Defects to minimize and report include internal compiler errors, panics, miscompiles, lowering or emission bugs, diagnostic bugs, and formatter or LSP drift encountered during implementation, review, or testing.