メニュー
Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/pellegre/libcrafter --skill prepare-prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.
Add or run deterministic libcrafter packet behavior validation through oracle specs, reference backends, offline checks, pcap checks, probe plans, and artifacts.
Use ignored .scratch workspaces for experiments, disposable prototypes, network probes, hardware exploration, generated code, and any task where the user asks for work that should not be committed until promoted.
SKILL.md を表示中
| 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,
validation, 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.