skills.rest
thimslugga
thimsluggaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

kernel-debug

Coordinate multi-agent workflows to analyze Linux kernel crashes and produce debug reports.

Updated Nov 29, 2025
Search Tags:#debugging#linux#kernel#call-graph#crash-analysis#semcode
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill kernel-debug-thimslugga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kernel-debug
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/linux/linux-review/kernel-debug
Command: npx skills add https://github.com/thimslugga/agent-skills --skill kernel-debug-thimslugga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Linux kernel debugging can be time-consuming and error-prone; this Skill coordinates multiple AI agents to systematically analyze crash reports, reproduce relevant contexts, and derive actionable root-cause hypotheses.

Core Features & Use Cases

  • Orchestrates a multi-agent workflow for kernel crash analysis (context gathering, code review, lore, and fixes tagging)
  • Loads kernel symbols, call graphs, and subsystem guides to ground analysis in real code
  • Produces a plain-text debug report suitable for kernel mailing list

Quick Start

Initialize a crash-investigation by feeding the crash report to the orchestrator and starting the multi-agent analysis workflow.

Frequently Asked Questions about kernel-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a Linux kernel crash trace using AI?▼

To analyze a Linux kernel crash trace, feed the oops or warning message to the orchestrator. It coordinates specialized agents to gather context, load kernel symbols, and derive actionable root-cause hypotheses from the call graph.

What is the best way to debug Linux kernel oops and warnings?▼

Debugging Linux kernel oops and warnings is best handled by a multi-agent workflow that loads subsystem guides and semcode-based symbol resolution. This grounds your root-cause analysis in concrete kernel code rather than guessing.

Can I generate a kernel mailing list debug report from a panic message?▼

Yes, you can generate a plain-text debug report suitable for the kernel mailing list from a panic message. The analysis workflow processes the crash trace and outputs a final report with actionable root-cause hypotheses.

Does this kernel debugging workflow require external dependencies?▼

No external dependencies are required to run this kernel debugging workflow. It operates independently using bundled scripts and references to coordinate agents for context gathering and symbol resolution.

How to coordinate multiple agents for Linux kernel crash analysis?▼

Coordinate multiple agents for Linux kernel crash analysis by initializing a crash-investigation with the orchestrator. It systematically distributes context gathering, code review, and fixes tagging across specialized agents to derive root causes.

Related Skills

Explore More Software Engineering Skills→
ryanbreenryanbreen
7

gdb-chat

Automate interactive GDB debugging sessions for the Breenix kernel.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
shysssthanhtrishysssthanhtri

gitnexus-exploring

Trace execution flows and call relationships in indexed GitNexus repositories.

Community
Intermediate
linfordWulinfordWu
1

vmcore-analysis

Analyze Linux kernel VMcore crash dumps and generate root-cause reports.

Community
Advanced