lwy-dispatch
lwy-dispatch coordinates three IDE-hook events (UserPromptSubmit, Stop, SessionStart) shared across learnwy skills, running their scanners in a single process instead of spawning separate Node instances per skill. It aggregates reminders from english-learner, llm-wiki, prompt-optimizer, knowledge-consolidation, and learnwy-status into one combined output per event, cutting per-turn hook latency and reducing system-reminder spam.
lwy-dispatch consolidates learnwy skill hooks into unified IDE events to reduce startup cost and context overhead.
AI-generated summary based on this skill's SKILL.md
Install
learnwy/skills/lwy-dispatch · repository language: TypeScript
git clone https://github.com/learnwy/skills
cp -r skills/skills/lwy-dispatch ~/.claude/skills/lwy-dispatchFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I consolidate multiple IDE hook events with lwy-dispatch?
lwy-dispatch consolidates three IDE-hook events (UserPromptSubmit, Stop, SessionStart) shared across learnwy skills into a single coordinated process. Instead of spawning separate Node instances per skill, lwy-dispatch runs all scanners in one process and aggregates reminders from english-learner, llm-wiki, prompt-optimizer, knowledge-consolidation, and learnwy-status into one combined output per event, eliminating duplicate system reminders.
What is the lwy-dispatch installation guide for IDE integration?
lwy-dispatch is an MIT-licensed hook coordinator designed for IDE integration. To install and configure it, follow the standard setup for learnwy dispatch coordinator configuration in your IDE environment. The tool acts as a single-process hook aggregator that replaces multiple skill-specific hook spawns, reducing startup latency and consolidating all event handling through one unified event coordinator.
How does lwy-dispatch reduce system reminder spam in Claude Code?
lwy-dispatch merges reminders from five learnwy skills (english-learner, llm-wiki, prompt-optimizer, knowledge-consolidation, learnwy-status) into a single combined output per IDE event. By running all skill scanners in one process instead of separate Node instances, lwy-dispatch eliminates duplicate system reminders and reduces context clutter from hook commands, cutting per-turn hook latency significantly.
How do UserPromptSubmit, Stop, and SessionStart events work in lwy-dispatch?
lwy-dispatch coordinates three core IDE-hook events: UserPromptSubmit (triggered on code submission), Stop (on session termination), and SessionStart (on session initialization). These three events are shared across all integrated learnwy skills. lwy-dispatch aggregates scanner output from each skill for each event type, merging their reminders into a single consolidated reminder per event rather than spawning separate processes.
What should I do if lwy-dispatch hook installation or event aggregation fails?
If lwy-dispatch hook installation or event aggregation encounters issues, verify that all five integrated skills (english-learner, llm-wiki, prompt-optimizer, knowledge-consolidation, learnwy-status) are properly registered in your IDE environment. Check that the single-process hook aggregator is running and that UserPromptSubmit, Stop, and SessionStart events are firing correctly. Ensure your IDE hook configuration points to the lwy-dispatch coordinator rather than individual skill hooks.
How does lwy-dispatch optimize hook startup performance?
lwy-dispatch reduces hook startup latency by consolidating multiple skill scanners into a single process instead of spawning separate Node instances per skill. This single-process hook aggregator approach eliminates redundant startup overhead, allowing UserPromptSubmit, Stop, and SessionStart events to execute faster while still delivering aggregated reminders from all five integrated learnwy skills in one combined output.
SKILL.md
rendered from the published skill — quoted content, verbatim
learnwy-dispatch
Single-process coordinator for the three IDE-hook events shared by the learnwy-* skills.
Why
Before this skill, every event fired N separate hook commands — one Node process per skill — and the user saw N back-to-back <system-reminder> blocks per turn. That multiplies the per-turn hook startup cost (~50 ms × N vs ~50 ms) and clutters context.
This skill replaces those entries with one hook per event that imports each skill's pure scanner function, runs them in-process, and emits a single combined reminder.
What runs per event
UserPromptSubmit (hooks/user-prompt-submit.cjs)
|
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 7 files
skills/lwy-dispatch/SKILL.md
skills/lwy-dispatch/hooks.json
skills/lwy-dispatch/references/conditional-reflection.md
skills/lwy-dispatch/scripts/cli.cjs
skills/lwy-dispatch/scripts/hooks/session-start.cjs
skills/lwy-dispatch/scripts/hooks/stop.cjs
skills/lwy-dispatch/scripts/hooks/user-prompt-submit.cjs