メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| 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"} |
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.
node dist/lfg.js --json setup --run or the exact command the user reported./tmp/lfg-source.gh issue list --repo islee23520/lfg --search "<short symptom>" --state open
lfg-generated label when available and end the body with the footer below.## 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.
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
MUST USE for planning before coding: 5+ steps, ambiguous scope, multiple modules, architecture decisions, a vague 'just make it good / figure out what to build' brief, or any request to plan, interview, or break work down. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode, just make it good, figure out what to build.
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
Persistent code-mode kernels (JS/Python) for incremental computation — omp/senpi eval analog on GrokBuild via lfg MCP. Use when multi-step code execution, data exploration, or stateful REPL beats one-shot bash.