From linux-debugging
Run targeted journalctl queries to surface only the relevant log lines for a debugging task — by unit, time window, priority, boot, or kernel/user scope. Emits structured output (JSON or short-form) suited for AI analysis. Use when the user reports a problem and you need to inspect logs without dumping everything. Assumes systemd + journald (Ubuntu, Debian, Fedora, Arch, etc.).
npx claudepluginhub danielrosehill/claude-code-plugins --plugin linux-debuggingThis skill uses the workspace's default tool permissions.
Targeted journalctl queries for AI-assisted debugging. The goal is to retrieve **just enough** log context — never `journalctl -xe` blindly, which floods the context window.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Targeted journalctl queries for AI-assisted debugging. The goal is to retrieve just enough log context — never journalctl -xe blindly, which floods the context window.
journalctl -u <unit> -b --no-pager -p warning
journalctl -b -1 --no-pager -p err
Requires persistent journald — verify with validate-persistent-journal if -b -1 returns nothing.
journalctl --since "10 min ago" -p warning --no-pager
journalctl --since "2026-04-28 14:00" --until "2026-04-28 14:30"
journalctl -k -b -p err --no-pager
journalctl -k --grep "(oom|segfault|oops|BUG|panic)" --no-pager
journalctl -u <unit> -b -p warning -o json --no-pager | jq -r '. | {t: .__REALTIME_TIMESTAMP, u: ._SYSTEMD_UNIT, p: .PRIORITY, m: .MESSAGE}'
JSON fields most useful for AI parsing: MESSAGE, PRIORITY, _SYSTEMD_UNIT, _PID, _COMM, __REALTIME_TIMESTAMP, SYSLOG_IDENTIFIER.
0=emerg 1=alert 2=crit 3=err 4=warning 5=notice 6=info 7=debug
Use -p N to include level N and below (more severe). Most debugging starts at -p warning.
journalctl with no filter — it's gigabytes.-f (follow) inside an agent session unless explicitly reproducing a live event; it blocks.--no-pager and then pipe to head — use -n <count> instead.-u <unit> so journald uses its index.After running a query, summarize:
Quote actual log lines verbatim when reporting suspicious entries — paraphrasing loses precision the user needs to grep their own system.