kernel-change

Name: kernel-change
Author: bengeek06

Use when implementing, fixing, or debugging VirtRTLab kernel modules, sysfs behavior, device lifecycle, or module load and unload paths in kernel/

by bengeek06(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from bengeek06/virtrtlab (.github/prompts/kernel-change.prompt.md). Copyright stays with the author.

Read the relevant contract first in README.md and the matching docs under docs/.

Then:

Read the affected kernel sources and build context before editing.
Make the smallest correct change that fixes the root cause.
Preserve Linux kernel coding style and current VirtRTLab naming rules.
Run make check, make qa-kernel-lint, and python3 -m pytest -c pytest.ini tests/kernel.
Before any PR, run python3 -m pytest -c pytest.ini tests/cli, python3 -m pytest -c pytest.ini tests/daemon, python3 -m pytest -c pytest.ini tests/kernel, and python3 -m pytest -c pytest.ini tests/install.
Summarize the behavioral change, validation, and residual risks.

If the contract is unclear or incomplete, stop and request a spec update before implementation.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Read the relevant contract first in README.md and the matching docs under docs/.

Then:

1. Read the affected kernel sources and build context before editing.
2. Make the smallest correct change that fixes the root cause.
3. Preserve Linux kernel coding style and current VirtRTLab naming rules.
4. Run `make check`, `make qa-kernel-lint`, and `python3 -m pytest -c pytest.ini tests/kernel`.
5. Before any PR, run `python3 -m pytest -c pytest.ini tests/cli`, `python3 -m pytest -c pytest.ini tests/daemon`, `python3 -m pytest -c pytest.ini tests/kernel`, and `python3 -m pytest -c pytest.ini tests/install`.
6. Summarize the behavioral change, validation, and residual risks.

If the contract is unclear or incomplete, stop and request a spec update before implementation.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

bengeek06-virtrtlab-kernel-change-prompt.prompt.jsonjson

{
  "prompt": "Read the relevant contract first in README.md and the matching docs under docs/.\n\nThen:\n\n1. Read the affected kernel sources and build context before editing.\n2. Make the smallest correct change that fixes the root cause.\n3. Preserve Linux kernel coding style and current VirtRTLab naming rules.\n4. Run `make check`, `make qa-kernel-lint`, and `python3 -m pytest -c pytest.ini tests/kernel`.\n5. Before any PR, run `python3 -m pytest -c pytest.ini tests/cli`, `python3 -m pytest -c pytest.ini tests/daemon`, `python3 -m pytest -c pytest.ini tests/kernel`, and `python3 -m pytest -c pytest.ini tests/install`.\n6. Summarize the behavioral change, validation, and residual risks.\n\nIf the contract is unclear or incomplete, stop and request a spec update before implementation.",
  "variables": [],
  "notes": "Use when implementing, fixing, or debugging VirtRTLab kernel modules, sysfs behavior, device lifecycle, or module load and unload paths in kernel/",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/bengeek06/virtrtlab",
      "path": ".github/prompts/kernel-change.prompt.md",
      "ref": "95d54b9d0c6ecb812989771f4735ba410c5b4541",
      "url": "https://github.com/bengeek06/virtrtlab/blob/95d54b9d0c6ecb812989771f4735ba410c5b4541/.github/prompts/kernel-change.prompt.md",
      "key": "bengeek06/virtrtlab/.github/prompts/kernel-change.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/bengeek06-virtrtlab-kernel-change-prompt/manifest?version=1.0.0

About

Use it

Manifest

Reviews