Commands

A command is a workflow you start by typing its name in your coding agent's chat, such as /wettaq show the last sync time on the settings page. Each is one Markdown file in commands/, shared by all three hosts; Codex runs them as $mexxi-<name> skills.

They are listed by how often you will use them: /wettaq for every change, then the ones you use once per repository or now and then.

Command	Why	When to use it
/wettaq	An agent saying it is done is only a claim, and checking its work yourself takes as long as writing it, so this brings back a pull request that has already been checked.	Use it for any change you would hand to a developer: a feature, a fix, or a follow-up on an open pull request.
/lesti	mexxi needs one pass/fail command to know when work is done, and most repositories do not have one ready, or have checks that already fail.	Use it once per repository, before your first /wettaq run.
/ittestja	Tests can pass while the page is still broken, because nobody looked at it in a browser.	Use it to see how a page, a flow or a pull request really behaves before you merge.
/fassal	Without written UX principles, every agent makes interface decisions its own way.	Use it when a product with a UI has no UX principles yet, or they need refining.
/sewwi	A change to one command, skill or rule can quietly contradict the others, so the workflow is changed as a whole.	Use it to audit or change the workflow itself: the commands, skills, agents and rules in your mexxi clone.
/irrifletti	Without measuring, you cannot tell whether a change to the workflow made runs better or worse.	Use it a couple of weeks after you change the workflow, to see whether runs got better.