kernel-debug-loop

Run time-bounded Breenix kernel sessions and detect log signals.

7|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/ryanbreen/breenix --skill kernel-debug-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kernel-debug-loop
Source: https://github.com/ryanbreen/breenix/tree/main/breenix-kernel-debug-loop
Command: npx skills add https://github.com/ryanbreen/breenix --skill kernel-debug-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Traditional kernel debugging often involves long boot times and manual log analysis, slowing down development. This Skill provides a rapid feedback loop by running the Breenix kernel in short, time-bounded sessions, automatically detecting specific log signals and terminating quickly. This dramatically accelerates iterative debugging and verification.

Core Features & Use Cases

  • Signal-Based Termination: Automatically stops the kernel when a predefined log message (signal) is detected.
  • Time-Bounded Execution: Limits kernel runtime to a specified timeout, preventing endless hangs.
  • Real-time Output Monitoring: Streams kernel logs directly to your console, providing immediate visibility.
  • Use Case: You're developing a new interrupt handler and need to quickly verify it initializes correctly. Use this Skill with a signal like "Interrupt handler initialized" and a 10-second timeout. The kernel will run, print its logs, and stop as soon as the signal appears (or timeout), giving you instant feedback on your changes.

Quick Start

Run kernel, stop when "KERNEL_INITIALIZED" appears (max 15s)

kernel-debug-loop/scripts/quick_debug.py --signal "KERNEL_INITIALIZED"

Run kernel for 30 seconds without specific signal

kernel-debug-loop/scripts/quick_debug.py --timeout 30

Run in BIOS mode, watching for "Boot complete"

kernel-debug-loop/scripts/quick_debug.py --signal "Boot complete" --mode bios

Frequently Asked Questions about kernel-debug-loop

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

FAQPage Schema
How do I speed up kernel debugging with automatic log monitoring?

Kernel debugging typically involves long boot cycles and manual log parsing. This Skill automates iterative kernel debugging by running time-bounded kernel sessions, detecting specific log signals, and terminating instantly when those signals appear or timeout is reached, dramatically accelerating your feedback loop.

Can I stop a kernel boot sequence when a specific log message appears?

Yes. Signal-based termination lets you configure a predefined log message (like "KERNEL_INITIALIZED") and the kernel stops automatically when detected, eliminating manual monitoring and reducing iteration time from minutes to seconds.

How do I verify kernel initialization checkpoints without waiting for full boot?

Configure the Skill with a targeted log signal matching your checkpoint and a short timeout window (default 15 seconds). The kernel runs, streams output in real time, and exits immediately upon signal detection or timeout, giving instant validation feedback.

Does this work with both BIOS and UEFI boot modes?

Yes. The Skill supports configurable BIOS and UEFI modes via the --mode flag, letting you test boot sequence behavior across different firmware types without switching tools.

What happens if the log signal never appears during kernel execution?

The kernel runs until the timeout limit is reached (configurable, default 15 seconds), then terminates with a clear exit status. This prevents infinite hangs and ensures predictable feedback on incomplete or failed initialization sequences.