danielrosehill/Claude-Code-Slash-Commands-Linux-Desktop

1You are analyzing system boot logs to identify failures and issues.2 3## Your Task4 51. **Analyze systemd boot logs** using `journalctl -b` to examine the most recent boot62. **Identify failures** by searching for:7   - Failed services (`systemctl --failed`)8   - Error and warning messages in boot logs9   - Services that timed out during boot10   - Failed units and dependency issues113. **Categorize issues** by severity:12   - Critical: Services that failed and are essential for system operation13   - Warning: Services that failed but are non-essential14   - Info: Services that are deprecated or can be safely disabled154. **Provide detailed analysis** including:16   - Service name and what it does17   - Exact error message from logs18   - Potential causes of the failure19   - Suggested remediation steps205. **Suggest cleanup actions** for:21   - Deprecated services that can be disabled22   - Unnecessary services slowing down boot23   - Configuration fixes for failed services24 25## Commands to Use26 27- `journalctl -b -p err` - Show errors from current boot28- `journalctl -b -p warning` - Show warnings from current boot29- `systemctl --failed` - List failed units30- `systemctl list-units --state=failed` - Detailed failed units31- `journalctl -u <service-name>` - Check specific service logs32- `systemd-analyze critical-chain` - Show boot time-critical chain33 34## Output Format35 36Present findings in a clear, organized manner:371. Summary of boot health382. Critical failures requiring immediate attention393. Warnings and non-critical issues404. Recommendations for cleanup and optimization415. Specific commands to fix identified issues42 43Be thorough but concise. Focus on actionable insights.44