Query Discord channel logs from cb-auto-buy service. Use this skill when debugging production issues, checking recent errors, finding purchase history, or investigating service behavior. Retrieves logs without needing SSH access.
Scan log files in ~/Library/Logs for PII leaks (emails, phone numbers, account numbers, names, addresses, SSNs, etc.). Use when verifying PII protection, auditing security, or checking for data leaks in application logs.
Post-session retrospective that analyzes what went well and what needs improvement. Produces actionable findings and optionally updates skills, MEMORY.md, or CLAUDE.md based on lessons learned.
Staff Engineer v2 — same engineering rigor as /staff-engineer but with 3-7x fewer tokens. Uses complexity-based routing, context packages, and inline diffs to eliminate redundant file reads across subagents.
Staff Engineer Swarm — same workflow as /se but uses agent teams (TeamCreate, SendMessage, TaskList) for persistent teammates, parallel research, and structured coordination. Best for MEDIUM/FULL complexity tasks.
Full-lifecycle engineering workflow with deep research, evaluator-optimizer planning, blast-radius analysis, conditional validation, and tiered iteration. Use for significant features, architectural changes, or any task that needs "the full engineering treatment."
Generate diagnostic HTML reports from utility-bill-manager sync logs. Analyzes logs for errors, identifies root causes, and creates a visual report in a temp directory. Use when debugging failed syncs, understanding why 0 bills were downloaded, or reviewing navigator behavior.
Create a git worktree for parallel development. Use when the user wants to work on a feature branch in a separate directory without switching branches.