Menu
Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Provision and use one disposable remote endpoint provider target for libcrafter packet work. Use for single-endpoint raw sends, captures, debugging, artifact collection, or endpoint teardown; use lab-session for coordinated multi-endpoint oracle/probe workflows.
Add or maintain libcrafter lab provider adapters, capability contracts, provider matrix tests, and documentation for substrate-independent oracle and probe execution.
Provision, use, collect, and tear down multi-endpoint libcrafter lab sessions across Hetzner, QEMU, VirtualBox, and future lab providers. Use when oracle, probe, or generated tools need provider-backed packet work that must be independent of the developer machine.
Add or run libcrafter packet behavior validation through oracle specs, backend adapters, offline checks, pcap checks, live checks, and artifacts. Use when packet behavior changes need validation coverage.
Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.
Use ignored .scratch workspaces for experiments, disposable prototypes, network probes, QEMU or dongle labs, generated exploratory code, and any task where the user asks to make a scratch folder or wants code/scripts that should not be committed until promoted.
| name | commit-changes |
| description | Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline. |
Use this skill whenever you create, amend, reword, split, squash, or otherwise prepare commits in this repository.
Every commit subject must use:
type(scope): subject
Allowed types:
build: build tooling, packaging, generated build metadatachore: repository maintenance that is not CI, docs, or testsci: GitHub Actions, workflow scripts, runner setupdocs: documentation-only changesfeat: new user-facing or API behaviorfix: bug fixes and reliability correctionsperf: performance improvementsrefactor: behavior-preserving code restructuringrevert: reverting a prior changestyle: formatting-only changestest: tests, fixtures, validation harnessesScopes are required. They are lowercase and may use digits, ., _, /, or
-.
Good examples:
feat(pcap): add nanosecond timestamp writer
fix(ci): install libpcap before workspace tests
test(interop): cover malformed tcp options
docs(live-lab): clarify Hetzner dry runs
Before committing, install the tracked hook once in the checkout:
.agents/scripts/install-git-hooks
Before rewording or pushing commit history, validate the affected range:
.agents/scripts/check-conventional-commits --range origin/master..HEAD
For a single proposed message, validate through the hook or checker rather than duplicating the regex by hand.
Stage only files that belong to the change being committed. Do not stage ignored artifacts, provider state, local credentials, generated reports, or unrelated user edits.
Keep commit subjects short, imperative, and specific. Put details in the body only when the subject cannot carry the reasoning.