zheref
@zheref
Public Skills
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 /spiritual-message [as turn landing], asks to see the report, or when /ren, /mukai or /en reaches its reporting step. Which blocks a variant renders is configuration; the dated final report is /backlog-board's.
gyo
by zheref
Lint the tree on every Ren turn — the named Hatsu process for the declared lint verb. Breath proves it on the fresh tip, rasengan may run it as authoring feedback, kokusen must run it over the finished tree before it commits, and aka runs it before squash and again after catch-up if the tree moved. It never measures coverage and never runs tests.
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 /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.
izanami
by zheref
Repeat a READ-ONLY task until a condition holds. Use when the maintainer invokes /izanami <task> until <condition>, or asks to watch, poll, or keep checking something until it changes. Observation only — it reads, reports and stops; it never writes to GitHub, never labels, never merges. For a loop that must act, use /izanagi, which requires an explicit iteration cap.
third-hand
by zheref
Harvest one sitting's process friction as Netero — propose 0–3 folded issues, file only what the maintainer picks, then end the session. Use after En has completed on the regular Kurapika pipeline, or when the maintainer invokes /third-hand while wrapping. Never merges, never implements the filed work. Not a step of En.
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 /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.
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.
black-voice
by zheref
Validate a delivered feature after its PR merges — resolve the PR and the issues it closed, take their acceptance criteria verbatim, raise Shalnark once to drive every one of them through ephemeral automated UI tests in the repository's own pinned tooling, and publish pass / fail / not-testable per criterion as a Rikugan page. Use when the maintainer invokes /black-voice [#<PR>], or asks for the merged feature to be validated against what was asked for. It is never automatic and never called from a composite; it fixes nothing, merges nothing, and files a failure only on the maintainer's word.
build
by zheref
Take one issue from wherever it sits to a delivery PR standing ready at its human gate. Use when the maintainer invokes /build #<issue>, or asks to build, start, release or deliver an issue. Kurapika confirms the mode, builds the issue himself — Hatsu holds no CI plane to route it to — and drives the resulting PR to CON-32 readiness, escalating a stuck effort to G5. Never merges, never applies a G1 mode label.
aka
by zheref
Send the branch out — gyo (lint) before rewriting history, squash only unpushed commits, bring the base underneath them, gyo again if catch-up changed the tree, and push. The whole skill runs only on the maintainer's publish call. It never runs project-wide tests or coverage; those belong to mukai through kotoamatsukami and byakugan.
bankai-quality
by zheref
Resolve the right adversarial-test tooling, performance-measurement tooling, and QA-{n} rules for a repo's bankai_scenario. Use before a release is cut, deployed, or published — when Phinks runs his adversarial pre-release QA, when Uvogin measures a performance budget, when authoring an E2E/adversarial test, or when either needs the scenario's pinned tooling before writing one.
breath
by zheref
Warm the local working copy once per effort — classify where the checkout sits, check the host toolchain, fast-forward the trunk and cut this effort's branch from its fresh tip, then prove the declared iteration checks pass on that tip, because a base that does not build is a G5 stop taken before any of the change is authored. Runs as the first turn of an effort inside ren; invoke it by name only to re-warm a drifted checkout. Never discards work it has not shown you, never commits, never pushes.
backlog-loop
by zheref
Drive a target repository's backlog to zero open actionable issues, in severity order, as gate-ready PRs. Use when the maintainer asks to work the backlog, clear open issues, run the loop, or keep a repo current. Kurapika triages, sequences build and sharingan across at most two efforts, cuts tags and runs the fan-out at severity-batch boundaries, and renders the per-cycle status board as a Rikugan. Never merges main; G2/G4/G3 stay the maintainer's.
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.
bankai-quality
by zheref
Resolve the right adversarial-test tooling, performance-measurement tooling, and QA-{n} rules for a repo's bankai_scenario. Use before a release is cut, deployed, or published — when Phinks runs his adversarial pre-release QA, when Uvogin measures a performance budget, when authoring an E2E/adversarial test, or when either needs the scenario's pinned tooling before writing one.
aka
by zheref
Send the branch out — gyo (lint) before rewriting history, squash only unpushed commits, bring the base underneath them, gyo again if catch-up changed the tree, and push. The whole skill runs only on the maintainer's publish call. It never runs project-wide tests or coverage; those belong to mukai through kotoamatsukami and byakugan.
bankai-handbooks
by zheref
Resolve the right Bankai handbook(s) for a repo/scenario — the always-load set plus exactly one stack handbook, with the rule-ID prefixes each one governs. Use when reviewing or building in a Bankai-consuming repo and you need the governing architecture/security/release rules, or need to cite a rule ID (UZF-/SEC-/UX-/REL-/QA-/SW-/KT-/RC-/BC-).
backlog-board
by zheref
Render the current backlog as the Kurapika gate board — the same sweep, arguments and gate assignment as /backlog-state, painted as a Rikugan page by nen report render --variant register instead of a markdown table. Use when the maintainer asks to see the board, the gate register, or the state as a page, or invokes /backlog-board <repo all>@<G1 G1-M G2 G3 G4 G5 all> [every <turn state-change once>] — the trailing clause makes the board re-render on every turn or whenever a scoped item's state changes, instead of the once-and-stop default. This skill also owns the render path futon, backlog-loop and the dated final report use. Strictly read-only — it never labels, merges, pushes, comments or opens anything.
byakugan
by zheref
Capture instrumented coverage and measure touched-file coverage at mukai, independently of unit, UI and integration tests. Kotoamatsukami runs those suites; gyo is linting. The declared coverage row may extract or parse a matching capture but must not rerun tests. Each test remediation invalidates evidence and returns through kokusen and kotoamatsukami before recapture and remeasurement.
backlog-loop
by zheref
Drive a target repository's backlog to zero open actionable issues, in severity order, as gate-ready PRs. Use when the maintainer asks to work the backlog, clear open issues, run the loop, or keep a repo current. Kurapika triages, sequences build and sharingan across at most two efforts, cuts tags and runs the fan-out at severity-batch boundaries, and renders the per-cycle status board as a Rikugan. Never merges main; G2/G4/G3 stay the maintainer's.
bankai-handbooks
by zheref
Resolve the right Bankai handbook(s) for a repo/scenario — the always-load set plus exactly one stack handbook, with the rule-ID prefixes each one governs. Use when reviewing or building in a Bankai-consuming repo and you need the governing architecture/security/release rules, or need to cite a rule ID (UZF-/SEC-/UX-/REL-/QA-/SW-/KT-/RC-/BC-).
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.
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-board
by zheref
Render the current backlog as the Kurapika gate board — the same sweep, arguments and gate assignment as $backlog-state, painted as a Rikugan page by nen report render --variant register instead of a markdown table. Use when the maintainer asks to see the board, the gate register, or the state as a page, or invokes $backlog-board <repo all>@<G1 G1-M G2 G3 G4 G5 all> [every <turn state-change once>] — the trailing clause makes the board re-render on every turn or whenever a scoped item's state changes, instead of the once-and-stop default. This skill also owns the render path futon, backlog-loop and the dated final report use. Strictly read-only — it never labels, merges, pushes, comments or opens anything.