| name | kernel-dev-skill |
| description | Linux kernel development skill grounded in local references/labs and references/lectures materials. Use for kernel modules, system calls, process scheduling, interrupts, locking, memory management, filesystems, networking, architecture, debugging, profiling, and device model work. |
Linux Kernel Development
Core rule: simple is superior to everything.
This skill is for practical kernel engineering. Use it to analyze failures, choose the smallest relevant subsystem material, make minimal verifiable changes, and validate with evidence.
Use this skill when
- Kernel code fails to build or run on a target kernel
- A module, subsystem patch, or lab skeleton needs implementation
- You need help on process, syscall, interrupt, SMP, memory, filesystem, networking, or architecture topics
- You are decoding oops/panic, lock bugs, memory bugs, or performance regressions
- You are working on device-model or driver-adjacent kernel paths
Scope
Includes:
- kernel modules and build flow
- kernel API and execution context rules
- system calls and process interactions
- interrupts and deferred work
- SMP and synchronization
- memory management and mapping
- filesystems and VFS-facing logic
- networking stack and net path basics
- architecture layer and portability concerns
- debugging and profiling
- device and driver model
Coverage contract
When responding, ensure the chosen path explicitly maps to one of these kernel components:
- module lifecycle
- syscall boundary
- process/scheduler path
- interrupts/deferred work
- locking/SMP behavior
- memory subsystem (allocation, mapping, lifetime, reclaim-facing assumptions)
