zheref
@zheref
Public Skills
mukai
by zheref
Take a pushed branch through catch-up, review, impacted tests, coverage and evidence to one open PR, render its landing report, then end by OFFERING to start En on the PR — one line naming /en on #<N>, never started silently — or, when nen/workflow.json → mukai.autoEn is true (absent means false), by starting En immediately in the same turn. En owns the capped current-head readiness loop through required CI and review. Mukai owns kotoamatsukami's unit/UI/integration tests and byakugan's coverage capture and gating. Gyo is linting on the Ren loop. Mukai gains no squash, first-publish, merge, or review-vote authority from nested phases.
jutaisho
by zheref
Ring the bell at the end of a turn — the three escalation rungs from nen/workflow.json (a push notification through the surface, an OS notification, an audible cue), the .nen/last-stop.json marker the Stop hook reads, and the in-session fallback where no hook is installed. Use when /ren reaches its sixth step, when /en reaches Ready, or when the maintainer invokes /jutaisho [at <gate>]. An ordinary turn rings rung 1 only, a turn that did nothing rings nothing, and a genuine gate gets all four parts of § 4 — the nen stop banner, the report link, lettered options with a star on the recommended decision, and the question through the surface's own option picker. Never prompts for /aka.
great-hiker
by zheref
Author and maintain canon prose and canon machinery in the governance and process repositories, and guarantee it lands on every supported surface with that surface's best capabilities (skills, personas, hooks, allowlists, rules files, model config). It is the writer /tenkai and the warm-up install from. Use when the maintainer invokes /great-hiker <request> [--effort low medium high] to change canon, or /great-hiker evolve [<surface>] to diff a surface's evolution guide against its cited official docs and file one Netero-shaped issue per drifted surface. Never edits surfaces/ by hand, never claims a capability without the fetched line quoted, never merges.
jujutsu
by zheref
Pair a new device with this machine and register it as a named launch target, once — walk the maintainer through the on-device steps, verify with the platform's own probe, then write the target into nen/contract.json and open the declaration PR at its repository's own gate. Use when the maintainer invokes /jujutsu pair <device>, asks to set up a new phone, tablet, simulator or desktop target, or when /amaterasu reports a launch target this machine cannot resolve. It never taps a trust prompt, never changes a security setting and never merges the declaration PR.
sharingan
by zheref
Drive one open PR to CON-32 readiness at its human gate, then stop there. Use when the maintainer invokes /sharingan #<PR> to <G2 G4>, or asks to get a PR ready, unstick a PR, or take it to the merge gate; /en composes it as its second and fourth steps. It names the first blocking condition, settles review threads, requests the owed reviewer round, and decides readiness with nen pr ready. It never merges, self-reviews, or votes.
tenkai
by zheref
Make a repository — new or existing, consumer or not — a working Hatsu consumer, deterministically and idempotently. It DIAGNOSES before it writes, reports what was satisfied, missing or drifted, repairs Hatsu-owned surfaces, and guides the owner through every remaining development-workflow decision. Use when the maintainer invokes /tenkai [<path>], asks to adopt, onboard or set up a repository, asks why a Hatsu skill does not work somewhere, or when /ten's verification reports an adoption item unsatisfied. The engine never writes a nen-owned declaration; the agent may configure a consumer's declaration after an owner decision and validation. It never invents a colour taxonomy, merges, pushes or opens a pull request.
susanoo
by zheref
Produce the distributable this repository declares — run the lane's own archive through nen shu archive, locally, and report every artifact it named by path and size. Runs inside /getsuga to build the release unit, and invoke /susanoo [--lane <lane>] by name to package a checkout on demand. It uploads nothing, publishes nothing and pushes nothing — where the consuming repository declares tags.identity it NAMES the tag kagutsuchi will cut on a successful upload, and cuts none itself; a lane that declares archive unsupported has its own reason quoted verbatim, and a missing signing identity is the declared precondition refusing, never a gap to fill — nen synthesises no signing material and neither does this skill.
getsuga
by zheref
Cut a release tag locally, end to end — preconditions, one folded release-proposal PR merged inside § 3a's bounds (or by the maintainer where they do not hold), the post-merge tag, then the CON-22 fan-out. Use when the maintainer invokes /getsuga [<hash branch-name main last-commit checkout>], or asks to cut a tag, cut a release, or ship a version. The cut point is never required: with no token it is origin/<branch.base> from nen/workflow.json (plain main when none is declared), stated with its source in the first line; a typed token always overrides, and a version-shaped token is read as the tag name. An off-main target is driven to main first, and susanoo builds the release unit. Merges exactly one PR itself — its own release-proposal PR, when its diff is the release unit only and CON-32 reads Ready, through the repository's own protection (the maintainer's ruling of 2026-09-26) — and never a delivery PR; never publishes a release — publication is mugetsu's, per target, at G3 — and never tags a commit unreachable from the configured trunk, origin/<branch.base>.
en
by zheref
Take one open pull request from the moment it opens to verified readiness and its merge (the run's own PR, at its terminus), under a mandatory acting-cycle cap — the landing report, fresh current-head observation, Sharingan remediation, catch-up when behind, and the bell only at Ready. Use when /mukai hands over its PR, or when the maintainer invokes /en on #<N> for a PR that is already open. Pending CI or review keeps the run active; quiet polls spend no cycle. En never merges and never casts a review vote. After this run completes, the regular pipeline's next phase is /third-hand — En does not own it.
tsukuyomi
by zheref
Execute the repository's declared focused tests for the behavior this turn actually changed. Rasengan may use it for feedback; kokusen must use it at every local checkpoint. It never runs project-wide regression, never measures coverage, and a test is never patched to pass.
mugetsu
by zheref
Publish one release to one production destination — a store, the live environment — by running the repository's declared release row (nen shu release) and/or nen shu deploy --target <production target> --run, after nen release preflight reads green and the tag has been cut. Use ONLY when the maintainer records a per-target go in their own words; that message is quoted verbatim in the report and on the release PR, and is never inferred. This is G3 (CON-6): no composite reaches it on its own authority — not getsuga, not en, and futon only as a typed then step carrying the ADVANCE GO its § 3 defines (the maintainer's own invocation, bound to the tag that run cuts, one target, once, and only on a repository nen repo classify reports as kind process or library) — no agent proposes it, a go with no tag is refused unless it is that advance go, and one go publishes one target once.
tensho
by zheref
Turn a dirty working copy into one PR standing ready at its gate. Use when the maintainer invokes /tensho <target-branch main>, or asks to branch this off, commit and PR what I have, or open a PR for these changes. Kurapika moves the work off main if needed, reviews every uncommitted file before staging it, commits, opens the PR with the body the template requires, then checks it against its gate. Never merges, never commits a file it flagged without an answer.
futon
by zheref
Work one selector of a repo's backlog — a severity band or one exact label — into PRs with an actor behind them, then run what follows then. Use when the maintainer invokes /futon <repo>@<severity[+] label> [then tag tag+fanout <skill>@<target> <prose>], or asks to work a band or a label. Kurapika scopes backlog-loop's engine to one selector; every PR is his own (Hatsu carries no CI plane), so done means CON-32 Ready and a per-PR merge prompt. Nothing after then runs before that; a typed then step is the maintainer's own call for the skill it names (the advance go, mugetsu § 3). Never merges main, never publishes a release itself.
file
by zheref
File one well-formed, correctly-labelled, non-duplicate issue — reconciling it against the open backlog first. Use when the maintainer invokes /file <problem> <repo> or a bare /file (which files what the session has just been discussing), or asks to file, open, log or raise an issue. Also execute the shared discovery protocol when authorized work exposes a durable workflow, machinery, or owner gap. Process-chairman findings — constitution, canon prose, machinery enhancement, duration, redundancy, autonomy gaps, deterministic jobs still done by hand, missing toolchain — are Netero's completeness contract (claude/agents/netero.md; Codex: the Netero section of AGENTS.md): every declared classifying label, observable acceptance criteria, and cross-references for deployment, fan-out and provisioning. Kurapika searches for duplicates to amend, near-neighbours to fold into, and issues this supersedes before writing.
kagutsuchi
by zheref
Send a build to a declared NON-PRODUCTION destination by running the repository's own deploy row through nen shu deploy --target <name> --run, behind a freshness gate — and, ONLY when the latest archive is not a build of the trunk's tip, run /susanoo first in a clean worktree at origin/<branch.base> with the maintainer's own gitignored files copied from core. Use ONLY when the maintainer invokes /kagutsuchi [<target>] or asks in their own words to upload this. The target is typed, or nen/workflow.json → deploy.defaultTarget; neither is asked as free text. The plan is printed always; sending happens only on that call — typed, or a futon then step on the advance go — never proposed. Production and the stores are /mugetsu at G3.
jujisho
by zheref
Split a mixed working copy into up to two stacked branches and PRs, by axis, leaving nothing behind. Use when the maintainer invokes /jujisho, or asks to split these changes, separate these concerns, or break this into separate PRs. Kurapika names every axis it finds, stacks the second PR on the first, states the merge order in both bodies, and asks which two when there are more. Never merges, never drops a hunk.
izanagi
by zheref
Repeat a task that ACTS until a condition holds, under a mandatory iteration cap. Use when the maintainer invokes /izanagi <task> until <condition> up to <N>, or asks to keep doing something until it is done. The cap is required grammar, not a default — an invocation without "up to <N>" is asked for the cap, which is never defaulted or derived. Each iteration runs under its own authority; a human gate ends the loop rather than being retried past.
hanten
by zheref
Have the change read adversarially pre-PR — classify with nen review scopes, raise one reviewer per raised scope with budget left, collect findings in one shape, settle each by fixing or pushing back with a cited reason. Use when the maintainer invokes /hanten [for <scope>], asks to review the branch, or at /mukai's review step.
kotoamatsukami
by zheref
Own impacted project-wide unit, UI and integration tests at mukai — run only the declared suites the change can affect, and handle UI evidence. Aka never runs this. Coverage capture and measurement are byakugan's. Gyo is linting. A skipped suite needs a named proof; an accepted snapshot invalidates the run.
ten
by zheref
Satisfy Hatsu's hard Nen dependency (D10) before any Nen-owned work — probe nen --version, read nen shu tools' verdict, install the pinned build through nen's checksum-verified bootstrap when absent or unsatisfied. Then refresh the checkout and mirrors, place the permission pack, and — given the calling phase — run its missing safe prerequisites (base, branch, catch-up, proof, auth, declarations), stopping at any that is the maintainer's call. Use first in every Hatsu session, as P1 of every phase, and when nen is missing.
shibari
by zheref
Compose the PR body from templates/pr-body.md and open the PR — the UZF-26 evidence table, the completion checklist, every associated issue and the agent-attribution ledger — then check it by verb and return the PR to mukai, which offers it to /en (or starts En under mukai.autoEn). Use when /mukai reaches its eighth step, or the maintainer invokes /shibari directly. It opens exactly one PR from the last pushed commit against the workflow's base, derives the gate but never labels one, requests reviewers, and never merges.
rasengan
by zheref
Author the requested change and its focused tests on the declared stack. It may execute the repository's declared scoped test lane for feedback and runs the inexpensive iteration checks while writing; kokusen owns the mandatory focused-test checkpoint. Rasengan runs as phase two of ren, commits nothing, pushes nothing, and never expands authoring into the full regression suite or coverage.
ren
by zheref
Run one request end to end as a turn — warm up on the first turn, author the change the request asks for, verify and commit it locally, launch the app, publish the report, ring the bell — and then wait for the next request. Use when the maintainer invokes /ren <request>, or simply asks for work in a repository where the turn loop is how work is done. Ren composes the six atomic skills by name and restates none of their protocol; it never pushes, never opens a pull request, and ends only when the maintainer calls /aka or /tensho.
murasaki
by zheref
Bring an already-published branch up to date with its base, rerun the shared iteration checks, and before pushing any source/test change return to the caller so kotoamatsukami can refresh impacted tests and byakugan can recapture coverage. Murasaki composes ao; it never independently owns tests, coverage, squashes, force-pushes, first-publishes, or opens a PR.