lfg-report-bug

Route lfg and GrokBuild adapter bugs into evidence-backed GitHub issues.

5|Updated May 17, 2026

Search Tags:#debugging #github #bug report #issue triage #reproduction #lfg #grokbuild

Ready to run

npx skills add https://github.com/islee23520/lfg --skill lfg-report-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lfg-report-bug
Source: https://github.com/islee23520/lfg/tree/main/skills/lfg-report-bug
Command: npx skills add https://github.com/islee23520/lfg --skill lfg-report-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn unclear lfg or GrokBuild adapter failures into a concrete, evidence-backed bug report that a maintainer can act on.

Core Features & Use Cases

Bug Triage: Investigate setup, sync, hook, MCP, agent, config, and plugin installation problems for lfg.
Evidence-Driven Reporting: Compare runtime behavior against the latest source and search for existing issues before drafting a report.
High-Signal Output: Produce a single GitHub issue or comment with reproduction steps, root cause, proposed fix, and verification plan.

Quick Start

Ask the assistant to investigate the lfg failure, reproduce it with the exact command you used, and prepare a maintainer-ready issue or comment if the problem is confirmed.

Frequently Asked Questions about lfg-report-bug

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

FAQPage Schema

How do I report a lfg setup failure or GrokBuild plugin installation issue?▼

To report a lfg setup failure, you reproduce the exact failing command, compare runtime behavior against source code, and generate an evidence-backed GitHub issue containing the root cause and verification plan.

What is the best way to triage lfg agent and config regressions?▼

Triageing lfg agent and config regressions involves searching for existing GitHub issues, reproducing the runtime error, and drafting a maintainer-ready comment with a proposed fix.

Can I use this approach for MCP breakage and hook sync problems in lfg?▼

Yes, this approach applies to MCP breakage and hook sync problems in lfg by routing the failure into a concrete bug report with reproduction steps and source comparison evidence.

Why does my lfg bug report need runtime reproduction before submission?▼

Runtime reproduction is required to confirm the lfg bug, compare actual behavior against the latest source, and ensure the final GitHub issue includes actionable evidence and a verification plan.

Does this bug report method work without checking existing GitHub issues?▼

No, searching for existing GitHub issues is a required step to prevent duplicates and ensure your lfg bug triage produces a high-signal maintainer comment rather than a redundant report.