ALWAYS READ
- Load
{{KERNEL_REVIEW_PROMPTS_DIR}}/technical-patterns.md
You consistently skip reading additional prompt files. These files are MANDATORY. This skill exists as a framework for loading additional kernel prompts.
Configuration
The review prompts directory is configured during installation:
- KERNEL_REVIEW_PROMPTS_DIR: {{KERNEL_REVIEW_PROMPTS_DIR}}
This variable is set by the installation script when the skill is installed.
Capabilities
Patch Review
When asked to review a kernel patch, commit, or series of commits:
- Load
{{KERNEL_REVIEW_PROMPTS_DIR}}/review-core.md - Follow the complete review protocol defined there
- Load subsystem-specific files as directed by review-core.md
Debugging
When asked to debug a kernel crash, oops, warning, or stack trace:
- Load
{{KERNEL_REVIEW_PROMPTS_DIR}}/debugging.md - Follow the complete debugging protocol defined there
- Use crash information as entry points into the code analysis
Subsystem Context
When working on kernel code in specific subsystems, load the appropriate
context files from {{KERNEL_REVIEW_PROMPTS_DIR}}/:
Always read
technical-patterns.mdbefore loading subsystem specific filesRead
{{KERNEL_REVIEW_PROMPTS_DIR}}/subsystem/subsystem.mdand load matching subsystem guides and critical patterns
Semcode Integration
When available, use semcode MCP tools for efficient code navigation:
find_function/find_type: Get definitionsfind_callchain: Trace call relationshipsfind_callers/find_calls: Explore call graphsgrep_functions: Search function bodiesdiff_functions: Identify changed functions in patches
Output
- Patch reviews produce
review-inline.txtwhen regressions are found - Debug sessions produce
debug-report.txtwith analysis results - Both outputs are formatted for the Linux kernel mailing list (plain text, 78 char wrap)