zheref
@zheref
Public Skills
backlog-state
by zheref
Render the current backlog as one gate-oriented table — every open issue with its associated PRs, for one repo or all of them, showing the human gate each item sits at, what it needs next, and which session is driving it. Use when the maintainer asks what the state is, what needs them, what is at a gate, or invokes $backlog-state <repo all>@<G1 G1-M G2 G3 G4 G5 all>. Strictly read-only — it never labels, merges, pushes, comments or opens anything.
amaterasu
by zheref
Build and start the app for the declared launch target from the maintainer's core working directory — never from a worktree — and hand back the exact command that did it, copied verbatim out of the dry run. Runs as phase four of ren; invoke /amaterasu [<target>] by name to relaunch or switch targets. A disconnected device is reported by its declared name and falls back only to the declared simulator; a session in a worktree reports the command instead of running it.
backlog-synthesis
by zheref
Reconcile a long backlog into a smaller one — group open issues that target the same rule/clause, machinery file or root cause, propose a consolidation plan as an iterable Artifact, and on approval file one consolidated issue, attach the originals as sub-issues and close them with a reference. Use when the maintainer invokes /backlog-synthesis <critical high medium low all> [<repo>], or asks to consolidate, synthesize, dedupe or shrink a backlog.
amenotejikara
by zheref
Swap which worktree the maintainer's core checkout holds, and swap back — list every checkout of the project with its branch, dirt and distance from the base, bring one worktree's committed tree into core so Xcode (or any IDE opened on core) and $amaterasu build and debug exactly that, and return core to where it started with its own uncommitted work restored. Use when the maintainer invokes $amenotejikara [list <worktree branch> [--take] return status], or asks to swap to a worktree, see what a worktree holds, debug a worktree from Xcode, or put core back. Core's work is parked in a pinned commit, never stashed; nothing is discarded, pushed or committed on anyone's behalf.
ao
by zheref
Bring the branch up to date with its base — rebase when nothing has been published, merge when it has, resolve the mechanical conflicts, and stop at G5 with both sides shown for a semantic one. Use when the maintainer invokes /ao [from <base>], asks to pull main in, catch the branch up, or rebase onto main, or whenever /aka, /murasaki or /en needs the branch current. Kurapika classifies every conflicted path before touching one and never picks a side on a conflict of meaning. Never pushes, never force-pushes, never rewrites a commit that is already on the remote.
backlog-state
by zheref
Render the current backlog as one gate-oriented table — every open issue with its associated PRs, for one repo or all of them, showing the human gate each item sits at, what it needs next, and which session is driving it. Use when the maintainer asks what the state is, what needs them, what is at a gate, or invokes /backlog-state <repo all>@<G1 G1-M G2 G3 G4 G5 all>. Strictly read-only — it never labels, merges, pushes, comments or opens anything.
amenotejikara
by zheref
Swap which worktree the maintainer's core checkout holds, and swap back — list every checkout of the project with its branch, dirt and distance from the base, bring one worktree's committed tree into core so Xcode (or any IDE opened on core) and /amaterasu build and debug exactly that, and return core to where it started with its own uncommitted work restored. Use when the maintainer invokes /amenotejikara [list <worktree branch> [--take] return status], or asks to swap to a worktree, see what a worktree holds, debug a worktree from Xcode, or put core back. Core's work is parked in a pinned commit, never stashed; nothing is discarded, pushed or committed on anyone's behalf.
spiritual-message
by zheref
Render one turn of work as a rich report (HTML page or native surface artifact), never a chat summary — the desk above the fold, the last turn, what landed and what did not, the delta graph, evidence, spend, launch, decisions. Use when the maintainer invokes hatsu:spiritual-message [as turn landing], asks to see the report, or when hatsu:ren, hatsu:mukai or hatsu:en reaches its reporting step. Which blocks a variant renders is configuration; the dated final report is hatsu:backlog-board's.
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 hatsu:tenkai [<path>], asks to adopt, onboard or set up a repository, asks why a Hatsu skill does not work somewhere, or when hatsu: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.
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 hatsu:ren reaches its sixth step, when hatsu:en reaches Ready, or when the maintainer invokes hatsu: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 hatsu:aka.
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 hatsu: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.
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.
sharingan
by zheref
Drive one open PR to CON-32 readiness at its human gate, then stop there. Use when the maintainer invokes hatsu:sharingan #<PR> to <G2 G4>, or asks to get a PR ready, unstick a PR, or take it to the merge gate; hatsu: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.
tensho
by zheref
Turn a dirty working copy into one PR standing ready at its gate. Use when the maintainer invokes hatsu: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.
izanagi
by zheref
Repeat a task that ACTS until a condition holds, under a mandatory iteration cap. Use when the maintainer invokes hatsu: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.
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.
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 hatsu:getsuga to build the release unit, and invoke hatsu: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.
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.
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.
hanten
by zheref
Have the change read adversarially before it is anybody else's problem — 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 hatsu:hanten [for <scope>], asks for a review of this branch, or at hatsu:mukai's review step.
kokusen
by zheref
Verify the finished tree and commit it locally. Run the shared iteration checks and, for changed executable behavior, the repository's explicit scoped test lane before staging. Refuse a red or missing focused route, then triage, format, and commit. Kokusen is the mandatory focused-test checkpoint; it never runs full regression or coverage and never pushes.
senkei
by zheref
Inventory a consuming product repo's own backlog — open epics, live integration branches, and open PRs — classify each effort, and drive every open PR to a CON-32/G2-readiness determination. Use when the maintainer asks for the status of a product repo (<product-repo-A>, <product-repo-B>, or any other Bankai consumer), wants its existing efforts driven forward, or invokes hatsu:senkei. Kurapika (Manipulator) enumerates the target repo's backlog, classifies each effort (delivering/building/stalled/queued/idle/undecidable), states a Ready/not-Ready call with the reason for every open PR, and reports one status table per pass. Carries no CON-25 delegation and never merges — G2 stays the maintainer's.
pr-state
by zheref
Report one PR's CON-32 readiness as the deterministic gate's verdict, quoted, with the conjunct-by-conjunct reason it passed or failed. Use when the maintainer invokes hatsu:pr-state #<N>, or asks whether a PR is ready, G2-ready, G4-ready or mergeable. Strictly read-only — it never labels, merges, pushes, comments or opens anything. A readiness claim made any other way is not a readiness claim.
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.