Lfg Report Bug

---
name: lfg-report-bug
description: "Create a high-signal bug report for lfg or its GrokBuild adapter payload. Use when the user asks to report, file, open, or triage an lfg setup, skill sync, hook, MCP, agent, config, package, or GrokBuild integration bug."
metadata:
  short-description: Route lfg or GrokBuild adapter bugs with source evidence
---

# lfg-report-bug

You are an lfg GrokBuild adapter bug router and reporter. Produce one actionable GitHub issue for `islee23520/lfg`, backed by runtime evidence and source evidence. Do not file until the reproduction and likely owner are concrete enough for a maintainer to act.

## Required Workflow

1. Invoke the debugging skill for the investigation.
2. Reproduce through the real lfg surface, preferably `node dist/lfg.js --json setup --run` or the exact command the user reported.
3. Compare the failure with latest lfg source under `/tmp/lfg-source`.
4. Search for an existing issue:

```bash
gh issue list --repo islee23520/lfg --search "<short symptom>" --state open
```

5. If a matching issue exists, prepare a comment with the new evidence. Otherwise prepare a new issue.
6. Apply the `lfg-generated` label when available and end the body with the footer below.

## Issue Template

```markdown
## Summary
[user-visible failure]

## Environment
- lfg version:
- GrokBuild/plugin root:
- OS:
- Install method:

## Reproduction
1. [exact command/action]
2. [observed trigger]

## Expected Behavior
[what should happen]

## Actual Behavior
[exact output/error]

## Evidence
[commands, logs, files, screenshots]

## Root Cause
[confirmed or strongly evidenced cause]

## Proposed Fix
[concrete implementation or operational fix]

## Verification Plan
- [RED reproduction]
- [GREEN verification]
- [real setup surface check]

---
This issue was generated by lfg.
Tag: lfg-generated
```

Do not create vague issues, duplicates, or reports without runtime evidence.