Run any Skill in Manus with one click

prepare-pr

Stars312

Forks87

UpdatedJune 14, 2026 at 14:30

Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.

Installation

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.

Run Skill in Manus

Source

pellegre

pellegre/libcrafter

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

Prepare PR

Use this skill whenever you open, update, title, review, or prepare a pull request for this repository.

Branch Name

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.

PR Title

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.

PR Body

Fill the template with:

a concise summary of behavior and scope
exact validation commands and their results
notes about any skipped validation or known residual risk

Do not mention internal agent workflow unless the user explicitly asks for it.

Merge Expectations

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.

More from this repository

same repository

endpoint-provider

pellegre/libcrafter

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.

2026-06-29312

lab-provider

pellegre/libcrafter

Add or maintain libcrafter lab provider adapters, capability contracts, provider matrix tests, and documentation for substrate-independent oracle and probe execution.

2026-06-29312

lab-session

pellegre/libcrafter

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.

2026-06-29312

packet-validation

pellegre/libcrafter

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.

2026-06-29312

scratch-work

pellegre/libcrafter

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.

2026-06-06312

commit-changes

pellegre/libcrafter

Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.

2026-05-26312

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.

Prepare PR

Use this skill whenever you open, update, title, review, or prepare a pull request for this repository.

Branch Name

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.

PR Title

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.

PR Body

Fill the template with:

a concise summary of behavior and scope
exact validation commands and their results
notes about any skipped validation or known residual risk

Do not mention internal agent workflow unless the user explicitly asks for it.

Merge Expectations

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.