菜单
Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.
| name | prepare-pr |
| description | 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 this skill whenever you open, update, title, review, or prepare a pull request for this repository.
Branches created for PR work must follow the repo-local create-branch skill:
kind/short-slug
Use typed names such as feature/complete-oracle or
fix/normalize-tcp-options, not bare task names such as complete-oracle.
The PR title summarizes the preserved commit series and must follow the same Conventional Commits policy as regular commits:
type(scope): subject
Allowed types are build, chore, ci, docs, feat, fix, perf,
refactor, revert, style, and test.
Scopes are required. Use the narrowest useful scope, such as ci, pcap,
live-lab, interop, docs, net, or a protocol family. Do not include PR
numbers, reviewer thanks, or branch metadata in the title.
Fill the template with:
Do not mention internal agent workflow unless the user explicitly asks for it.
PRs should be rebased onto the latest protected base branch and then landed by fast-forwarding the base branch to the PR head. Do not use GitHub squash merge for normal PR landing.
Every commit in the PR range must pass:
.agents/scripts/check-conventional-commits --range origin/master..HEAD
If a PR targets a renamed default branch such as main, substitute that base in
the range.
If a PR accumulates noisy work-in-progress commits, fix up, squash, or reword them before marking the PR ready, then rebase again onto the latest protected base.