Latest stable
Log Scanner
Detect known Python, Node.js, fatal, and resource errors and turn them into kanban bug reports.
When to use it
Logs are durable enough to scan and deduplicated findings should enter the task queue.
When not to use it
Do not treat pattern matching as proof of root cause or scan secret-bearing logs without review.
Prerequisites
Readable logs; ripgrep is preferred with grep fallback.
Representative command
Safety contract
Preview with --dry-run before task creation; reset state only when intentional re-scanning is acceptable.
Artifacts to inspect
Scanner state and generated kanban tasks containing matched error context.
Troubleshooting
Use --status to inspect scan state and --reset only to deliberately re-scan all input.
Freshness source
Reviewed against YYLO README: log-scanner and the generated installed-script inventory.