القائمة
Create, rename, check out, or prepare libcrafter branches and worktrees with typed branch names such as feature/slug or fix/slug instead of bare task names.
التثبيت باستخدام 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.
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 | create-branch |
| description | Create, rename, check out, or prepare libcrafter branches and worktrees with typed branch names such as feature/slug or fix/slug instead of bare task names. |
Use this skill whenever you create, rename, check out, or prepare a branch or worktree for repository work.
Use:
kind/short-slug
Allowed kinds:
feature: new behavior, capabilities, protocol support, tooling, or planned
feature workfix: bug fixes, regressions, correctness issues, reliability fixesdocs: documentation-only worktest: tests, fixtures, validation harnesses, oracle coverageci: GitHub Actions, hooks, commit policy, runner setupchore: repository maintenance, dependency hygiene, generated metadatarefactor: behavior-preserving restructuringperf: performance improvementsrelease: release preparation and publish plumbingKeep slugs lowercase ASCII, hyphen-separated, and specific enough to identify the work. Prefer 2-5 words. Do not use spaces, underscores, uppercase letters, PR numbers, personal names, timestamps, or bare plan names.
Good examples:
feature/complete-oracle
fix/normalize-tcp-options
test/oracle-pcap-fixtures
docs/release-checklist
ci/conventional-commit-policy
release/crafter-0-1
Bad examples:
complete-oracle
oracle
agent-work
fix stuff
feat_complete_oracle
When a tool proposes a bare plan or task branch such as complete-oracle,
convert it to the nearest typed branch, usually feature/complete-oracle for
new capability work or fix/<slug> for corrective work.