Use when working with b4 for kernel patches: applying a series from lore (b4 am, optionally as stg patches via stg import), or preparing and sending your own series (b4 prep / b4 send) -- enrolling a branch, editing the cover letter and changelog, populating To/Cc from MAINTAINERS, and dry-running or sending. Covers…
Kernel debugging with drgn, live or from a crash dump. Guides inspection of /proc/kcore, per-cpu variables, stack traces, slab caches, and data structure traversal. Covers correct API patterns, type introspection, containerof usage, and common pitfalls for SUNRPC, NFS, and AIO subsystems. Also covers opening kernel…
Load when the user asks to find, read, or interpret reviews from the sashiko kernel-patch review bot, or when they reference sashiko.dev. Also load when a lore search for bot reviewer output returns empty, or fetching sashiko.dev returns only the SPA app shell -- this skill covers those failure signatures and the…
Use whenever you are about to query semcode -- any mcpsemcode tool, the semcode CLI, or semcode-index -- to look up functions, types, callers, call chains, or commits, or to search the local lore mailing-list archive. Load it BEFORE the first call, not after one goes wrong, and even when a sibling skill (sashiko, b4…
Load when committing, amending, rebasing, or managing patches in any repository that uses StGit (stg). Required whenever the user asks to commit changes, update a commit, create or edit a patch, reorder patches, or resolve merge conflicts on a branch with an active stg stack.
Use when writing, editing, or reviewing a code comment in any codebase -- calibrating a comment's voice and verbosity, deciding whether a comment earns its place, judging whether to comment at all, or writing an API documentation block (kernel-doc, rustdoc, a docstring). Linux kernel trees take references/kernel.md on…
Use when writing, amending, or rewording a git commit message in any repository -- drafting the log for a new commit, rewriting an stg patch's description, or fixing up a message before pushing or sending. Covers subject-line form, the why-first body, trailers, line widths, and the prose voice. Reach for this whenever…
Use when composing, editing, or reworking the content of a document that introduces a set of changes to the people who will review them -- a Linux kernel patch series cover letter (the [PATCH 0/N] blurb), a GitHub pull request description, or a merge commit message taking a topic branch. Load this whenever you decide…
Use when drafting or editing prose written for other developers -- a code comment in any codebase, a commit message in any repository, or a patch series cover letter, version changelog, pull request description, or merge commit message. Carries the voice rules the cel-prose:code-comments, cel-prose:commit-message…
Use when writing or reworking the per-version changelog of a rerolled patch series -- the "Changes in vN:" block, with its "Link to v(N-1):" line, that b4 places below a "---" divider at send time. Load it whenever a v2-or-later posting needs its list of what changed since the previous one -- "write the changelog"…