MIMIC Troubleshooter
This skill helps you diagnose and fix common issues in the MIMIC VS Code extension development workflow.
When to Use
- •User reports "stuttering" or "lag" (performance issues).
- •Build or Packaging (
vsce package) fails. - •Extension features (like the sidebar or shell hook) are not appearing or working.
- •You need to verify the integrity of the project environment (node_modules, out folder).
Workflow
1. Quick Diagnosis
Run the diagnosis script to check for common signs of trouble:
bash
./.agent/skills/mimic-troubleshooter/scripts/diagnose.sh
2. Common Fixes
Build Failures
- •Symptom:
npm run compilefails orvsce packageerrors. - •Action: Check
problemsin the IDE or runnpm run compilemanually to see TS errors. - •Common Cause: Duplicate variable declarations (e.g.,
outputChannel), missing imports, or interface mismatches.
"Stuttering" / Performance
- •Symptom: User says the agent is slow or "berbucking" (Korean for stuttering/lagging).
- •Action:
- •Check if
ActivityWatcheris flooding logs to~/.mimic/events.jsonl. - •run
tail -f ~/.mimic/events.jsonlto see if it's spamming. - •Check
Extension Hostlogs in VS Code for infinite loops or frequent errors.
- •Check if
Shell Hook Not Working
- •Symptom: Commands not logging.
- •Action:
- •Check
~/.zshrcforsource .../mimic-zsh.sh. - •Verify
mimic.enableRealtimePerceptionistruein settings. - •Run
source ~/.zshrcmanually.
- •Check
Reference
See COMMON_ERRORS.md for a database of known error patterns and solutions.