gates
Skill9 starsChanged 2 days agoMITView on GitHub
Run the pohunek CI gate set locally and report the results honestly. Use before declaring any Rust change done, when a branch must be verified as building, or whenever a run of the repository gate set is requested. This is the shared verification block the milestone, milestone-review, merge-advance, and release skills all rely on.
- Reads credentials
- Installs packages
10 other projects use a version of this.
Adopted by
Most recently taken up by
- akshaypimprikar/pragmatheir own version, first seen Nov 11, 2026
- FiredMosquito831/my-writing-companiontheir own version, first seen Nov 1, 2026
- CorvusWing/CorvusWingtheir own version, first seen Oct 25, 2026
- harshanandak/forge-legacytheir own version, first seen Oct 17, 2026
- Fadi88/one-man-startuptheir own version, first seen Oct 15, 2026
- The-40-Thieves/obsidian-tctheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Nebulock-Inc/agentic-threat-hunting-framework★ 420same name
- Fadi88/one-man-startup★ 16same name
- The-40-Thieves/obsidian-tc★ 13same name
- akshaypimprikar/pragma★ 4same name
- harshanandak/forge-legacy★ 4same name
- FiredMosquito831/my-writing-companion★ 2same name
- CorvusWing/CorvusWing★ 1same name
- Leostruka/devin-bundle★ 0same name
- ninoverse/claude-mit-go-template★ 0same name
- ninoverse/claude-mit-rust-agent-template★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ms-rustSkill
- contributeSkill
- coordinateSkill
- deliver-issueSkill
- github-workflowSkill
- merge-advanceSkill
- milestone-reviewSkill
- milestoneSkill
- plan-phaseSkill
- pr-handoffSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run from the workspace root.
- Very specific: line 112
Never retry the step to green and never lower --count to pass.
- Very specific: line 115
Add --slow-runner when a changed test in a heavy or macOS-lane package persists state, or when any test was reported flaky only on the …
- Very specific: line 138
Run from the repository root (see .agents/instructions/verification.md for the full commands): bun install --frozen-lockfile, bun run …
- Distinctive: line 147
Run each command in order.
- Distinctive: line 149
If a step fails, capture the failing output and fix the cause (or delegate the fix).
- Very specific: line 184
Every other POHUNEK_* name is contributor or CI configuration (for example POHUNEK_PYTHON_BIN, which selects the Hermes test interpreter): …
- Distinctive: line 200
No receipt file exists for the key, or it is not valid JSON of the known schema.
- Very specific: line 237
Use these to shorten the feedback loop (see .agents/instructions/verification.md "Fast loops" — cargo t, cargo tw, python3 …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
gates — run the CI gate set
CI is the source of truth for this repo. This skill mirrors the repository
verification guide (.agents/instructions/verification.md) and the current CI gate set, in the
same order, so a local pass lines up with what CI will run. Never claim a gate
passed without running it; report failures with the real command output. The
verification guide is the current inventory — including SDK workspace gates,
the real-daemon suite, and cargo xtask hermes compatibility — and always wins
over this procedural summary.
Core gate set
Run from the workspace root. clippy and docs check run with warnings as
errors, mirroring CI. Run them on the CI toolchain: with the rustup proxies
($CARGO_HOME/bin, default ~/.cargo/bin) first on PATH, rustup selects the
rust-toolchain.toml pin for rustc, clippy and rustfmt alike. A
distribution toolchain earlier on PATH ignores the pin, so its clippy and fmt
results are not gate evidence; the rustc-pin row of scripts/dev-bootstrap
flags a differing rustc.
cargo fmt --all --check
scripts/check-rust-toolchain-pin # no floating Rust channel in CI
cargo clippy --workspace --all-targets --all-features # under -D warnings
scripts/darwin-check # macOS-only code; needs zig on a Linux host
cargo build -p pohunek-session-worker --bin pohunek-sessiond
scripts/heavy-run cargo nextest run --profile ci --test-threads 16 --workspace --all-features
# Sixteen threads only through scripts/heavy-run (see "Heavy runs" in
# docs/development.md): measured ~150 s for the full workspace suite
# (7764 tests) on the 24-CPU host, against ~686 s at 4 threads. Twenty
# threads averaged slower (173 s) and flaked under load
# (#2267, #2268; #2269 at sixteen).
# `cargo tw` runs four test processes on plain `TMPDIR`; the gate count
# never goes through `tw`.
cargo test --doc --workspace --all-features # nextest excludes doctests
cargo build --workspace --release
cargo xtask docs check
scripts/build-hermes-package /abs/path/to/hermes.tar.zst
cargo xtask hermes compatibility --bin-dir /abs/path/to/target/release \
--package /abs/path/to/hermes.tar.zstA local pass does not guarantee CI green — shard partitioning, macOS jobs, and CI-only services make CI the arbiter — but these are the same commands CI runs. Skipping a command is never silently green: a gate that genuinely cannot run in this environment (missing pinned Hermes executable) is a failed/skipped gate to report explicitly, with the reason.
cargo xtask docs check validates the assistant knowledge bundle (schema,
knowledge-log fragments, drift, source-map, the shape of the assistant prompt
contract, runbooks, secret scan, release extras, command examples against the
clap tree, the crate table, the package lists and the documentation index). Run
it for every change; it is mandatory when the change touches anything under
docs/knowledge/, a CLI command/flag, a protocol method/event, or
docs/public-api.md.
Stress the changed tests
Mandatory when the diff (committed, staged or unstaged) adds or changes a Rust
test in a heavy or macOS-lane package or file: any test outside the
profile.fast default-filter in .config/nextest.toml (the complement of its
not ( ... ) expression is the heavy partition). Run it after the core gate
set passes and before push, with the profile that owns the tests:
scripts/stress-changed-tests --base origin/main --count 50 --deadline 45m --profile heavy
scripts/stress-changed-tests --base origin/main --count 50 --deadline 45m --profile macos --unpinned # macOS hostsIt builds the test binaries first (cargo nextest list), then runs exactly the
changed tests N times under scripts/stress-run (4 pinned CPUs, no retries).
Counts are lane suggestions, not defaults: 50 for heavy; pick
the deadline from the measured cost of one iteration. On macOS there is no CPU
affinity, so the run needs --unpinned and the contention is host-wide; say so
in the report. Both cargo calls share one -p package set, taken from the full
selection, so the run does not rebuild with a different feature unification.
They build with --all-features, like CI's Linux test archive, so
feature-gated tests run. CI's macOS lane and tier
archives build default features, so under --profile macos the step builds
default features too: a test that exists only behind a Cargo feature is not in
the list, because CI's macOS lane never builds it either. Without
--allow-missing-on-host it fails by name; with the flag it is reported NOT
STRESSED and belongs to the Linux run that builds it with --all-features.
--print shows the selection without running anything. With --slow-runner it
prints the per-test SLOWED/NOT SLOWED assignment
(slow-runner: SLOWED <binary_id> <name> /
slow-runner: NOT SLOWED <binary_id> <name>) plus the two whole-selection
split filters, which it derives by running cargo nextest list
(-E '(<selection>) and (<union>)'), so it builds the selected test binaries. A test
the script cannot map or list fails the step by name; a macro_rules! that
generates tests fails by the macro's name (stress the whole partition then). A
diff that changes tests for two operating systems cannot pass on one host: run
the step on each host with --allow-missing-on-host, which names every test the
host does not build as NOT STRESSED, and carry those names to the host that
builds them in the report. The flag excuses only a test with a non-test cfg
on its declaring chain (its own attributes, enclosing inline modules, the
file's #![cfg], the mod x; declarations above it); a missing test under
plain #[cfg(test)] still fails.
A failure is a FLAKY result under the flaky-test policy: open or reuse an issue
with the root cause, fix the test or the product race, and run the step again.
Never retry the step to green and never lower --count to pass. A diff that
adds no test in those lanes skips the step, and the report says so.
Add --slow-runner when a changed test in a heavy or macOS-lane package
persists state, or when any test was reported flaky only on the macOS runner.
It reproduces the slower CI macOS runner on a Linux host: the run is pinned to
3 CPUs and every fsync/fdatasync is delayed by 8.3 ms through
strace --seccomp-bpf --inject=...:delay_enter=8300. Tests listed in
scripts/stress-slow-runner-untraced.json are too ptrace-sensitive to run
under strace, so they still run pinned to 3 CPUs but untraced, and the summary
reports them as NOT SLOWED <binary_id> <name>; every other selected test runs
under strace and is reported as SLOWED <binary_id> <name>. NOT SLOWED means "ran
pinned but not slowed", never
"skipped": a NOT SLOWED failure is a FLAKY result like any other. To extend
the list, add one entry with filter (a nextest filterset matching the test),
a non-empty reason, and evidence (an issue comment with the hang
measurement, for example the strace -f -c hang count on #2213); keep the filters exact so no other test loses its slowdown.
--slow-runner is Linux-only and conflicts with --unpinned. Each
of the two runs gets the full --deadline, so the wall time can reach
twice the deadline. A deadline
overrun of the traced run under --slow-runner hints that a newly hanging
test may belong on the untraced list: rerun the suspect without
--slow-runner to confirm, then list it with evidence.
When the change touches the SDK workspace
Run from the repository root (see .agents/instructions/verification.md for
the full commands): bun install
--frozen-lockfile, bun run typecheck, bun run lint, bun test, and
bun test sdk/ts/scripts (the SDK release pack contract). The real-daemon suite runs
with the built pohunekd/pohunek-sessiond/pohunek binaries when the
change can affect daemon/worker behavior.
How to run it
- Run each command in order. Stop reporting a step as green only after it exits 0.
- If a step fails, capture the failing output and fix the cause (or delegate
the fix). Re-run the failed step and every step whose inputs the fix
changed; a step whose inputs are unchanged keeps its result, and a fix to
workspace-wide inputs (
Cargo.toml,Cargo.lock,.config/nextest.toml, the CI workflow) re-runs the whole set. The reported set must hold for the final revision: every step's evidence was produced on inputs identical to it (testing policy (.agents/instructions/verification.md#testing-policy)). - Report a compact status per gate (pass / fail + first failing lines, or explicitly skipped with why). Say plainly what actually ran. If all pass, say so plainly; if any fail or were skipped, say which and why, with output.
Receipts
scripts/gate-receipt run --gate <name> --max-age 24h -- <command> wraps one
canonical gate line so a second run on an unchanged tree skips the command.
The first run executes the command and writes a receipt; the second verifies
the receipt and exits 0 without running it. A receipt is local convenience,
never CI evidence: CI and the Opus review marker stay the landing evidence.
Wrap each gate with its canonical line, identical across sessions so the key
matches (the argv after -- is part of the key):
scripts/gate-receipt run --gate fmt --max-age 24h -- /tmp/heavy-run.sh cargo fmt --all --check
scripts/gate-receipt run --gate toolchain-pin --max-age 24h -- /tmp/heavy-run.sh scripts/check-rust-toolchain-pin
scripts/gate-receipt run --gate clippy --max-age 24h -- /tmp/heavy-run.sh cargo clippy --workspace --all-targets --all-features
scripts/gate-receipt run --gate darwin --max-age 24h -- /tmp/heavy-run.sh scripts/darwin-check
scripts/gate-receipt run --gate nextest --max-age 24h -- /tmp/heavy-run.sh cargo nextest run --profile ci --test-threads 4 --workspace --all-features
scripts/gate-receipt run --gate doctests --max-age 24h -- /tmp/heavy-run.sh cargo test --doc --workspace --all-features
scripts/gate-receipt run --gate docs --max-age 24h -- /tmp/heavy-run.sh cargo xtask docs checkgate-receipt strips the daemon's session runtime names from the wrapped
command's environment and keys no session runtime name, so no unsetting is
needed around the invocation and receipts are shared across sessions.
Every other POHUNEK_* name is contributor or CI configuration (for
example POHUNEK_PYTHON_BIN, which selects the Hermes test interpreter):
it passes through to the gate unchanged and is keyed by hash, so a changed
value reruns the gate.
The final gate before a push may use a receipt only when that receipt was written for the exact tree being pushed; a receipt never carries a gate across a changed tree.
24h matches the lane rhythm: a receipt written during the day's work is still fresh for the evening's final gate or the next morning's re-run, while a tree that sits longer than a day re-runs its gates instead of trusting stale proof from a toolchain or dependency world that may have moved.
A receipt is not accepted — the command runs again — when any of these holds:
- No receipt file exists for the key, or it is not valid JSON of the known schema.
- The key differs: a changed working tree (tracked, staged, unstaged, or
untracked-but-not-ignored files), a different gate name or argv, a
different working directory, different
rustc -vV/cargo -vVoutput, a different command-file hash, a differentCARGO_HOMElocation, extra compiler flags or wrappers (RUSTC,RUSTC_WRAPPER,RUSTC_WORKSPACE_WRAPPER,CARGO_ENCODED_RUSTFLAGS,RUSTC_BOOTSTRAP), or different tracked environment hashes. The daemon's session runtime names are never keyed, so a second session reuses the receipt; every otherPOHUNEK_*name is configuration and is keyed, so a changed contributor setting reruns the gate. - It is older than
--max-age, or it ends more than 60s in the future (beyond theCLOCK_SKEW_SECONDSclock skew bound). - It is not owned by the current uid, or it is readable or writable by group or others.
- The store directory is not owned by the current uid, or is not mode 0700.
A wrong store mode is never repaired silently: both
runandcheckrefuse the receipt,runruns the command and writes no receipt. - Ignored inputs are out of scope by construction:
target/, local.envfiles, and other ignored paths never enter the tree id, so changing only them never invalidates a receipt. - A gate that needs the network or external state is never wrapped: the
two Hermes gates (
scripts/build-hermes-package,cargo xtask hermes compatibility) andcargo auditre-run every time. Their inputs live outside the key — the package tarball, the--bin-dirbuild outputs, the remote registry — so a receipt could skip a gate whose real inputs have moved. - A gate whose output under an ignored path feeds a later gate is never
wrapped:
binsbuildspohunek-sessiond, which the nextest daemon tests spawn from beside the test binaries, andrelease-buildfillstarget/release, which the Hermes compatibility gate reads through--bin-dir. Both outputs live under the ignoredtarget/, outside the key, so a skipped producer would leave a missing or stale artifact that a later gate consumes. Build them every time.
Narrower loops while iterating
Use these to shorten the feedback loop (see
.agents/instructions/verification.md "Fast loops" —
cargo t, cargo tw, python3 scripts/test-partitions run <shard>),
but always finish with the full set above.
The default inner-loop command is cargo t. cargo ta (cargo xtask
affected) is the CPU-saving option when several agents or worktrees share
the host: the fast tests of the crates the branch and working tree touch,
plus their dependents, escalating to everything for workspace-wide or unmapped paths.
cargo ta --print shows the per-file reasons. It is never a substitute for
any gate above.
Extra CI jobs (only when your change touches deps/features)
cargo audit
cargo hack --feature-powerset --workspace clippy --all-targets
cargo shear --locked --deny-warnings # stable; PR gate
cargo +nightly-YYYY-MM-DD udeps --workspace --all-targets --all-features # optional; CI: main/nightlyThe udeps date is the pinned nightly: the toolchain: nightly-YYYY-MM-DD
input of the cargo-udeps job in .github/workflows/ci.yml.
Install the versions CI pins (CARGO_HACK_VERSION and CARGO_UDEPS_VERSION
in the .github/workflows/ci.yml env; a bump changes both places, and
PinnedInstallToolTests compares them): cargo install --locked
cargo-hack@0.6.46 and cargo install --locked cargo-udeps@0.1.61.
Note: knowledge gates its protocol bridge behind a protocol feature, so
--all-features only covers the everything-on case — the feature-powerset job
is what catches a broken feature combination.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

