kernel-verify

Validate kernel patch review findings and output VERIFIED ISSUE or ELIMINATED.

Updated Nov 29, 2025

Search Tags:#kernel #code-review #false-positives #patch-review #bug-verification #verification-checklist #linux-kernel

Ready to run

npx skills add https://github.com/thimslugga/agent-skills --skill kernel-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kernel-verify
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/linux/linux-review/kernel-verify
Command: npx skills add https://github.com/thimslugga/agent-skills --skill kernel-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verify kernel patch review findings and eliminate false positives. Use after kernel-review or kernel-debug to validate that reported issues are real bugs with concrete evidence. Activates in Linux kernel source trees.

Core Features & Use Cases

Systematically verify kernel patch reviews to ensure issues are real bugs with concrete evidence.
Load reference materials and apply a structured verification checklist to separate true issues from false positives.
Improve reliability of kernel changes by validating patches in the Linux kernel source tree before submission.

Quick Start

Load the references and apply the verification checks to confirm reported issues.

Frequently Asked Questions about kernel-verify

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

FAQPage Schema

How do I verify Linux kernel patch review findings and eliminate false positives?▼

To verify Linux kernel patch review findings and eliminate false positives, apply a structured verification checklist to validate reported issues in the source tree, classifying each as a verified issue or eliminated with supporting evidence.

What is the best way to confirm if a reported kernel bug is a real issue?▼

The best way to confirm a reported kernel bug is to apply a structured verification checklist against the Linux kernel source tree, loading technical pattern references to validate the finding with concrete evidence before submission.

Do I need to run a kernel patch review before verifying reported issues?▼

Yes, this verification step should be used after running kernel-review or kernel-debug steps to validate that the reported issues found during those initial patch review phases are real bugs.

How does a structured checklist help separate false positives from real kernel bugs?▼

A structured verification checklist helps separate false positives by loading technical pattern references and false-positive guides to systematically analyze reported kernel issues, ensuring only real bugs are validated with concrete evidence.

Can I validate kernel patch findings outside of a Linux kernel source tree?▼

No, this verification process activates specifically within Linux kernel source trees to systematically validate patch review findings and distinguish real bugs from false positives using targeted technical references.

What output should I expect when validating false positives in kernel patches?▼

When validating false positives in kernel patches, the verification process outputs either VERIFIED ISSUE or ELIMINATED status, providing supporting evidence to confirm whether the reported bug is real.