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