--- name: journal-checks description: Load it when a check is created, run or fails. Scripts that say pass or fail about the project, run on demand or on a schedule of their own; a failure is filed and told to the agent. keywords: checks, check commands: checks --- # Checks Scripts that say pass or fail about the project, run on demand or on a schedule of their own; a failure is filed and told to the agent. A check is a row of its own: journal check create "" --set command="" --set every=. It runs as its own process from the project root, never inside the server; exit 0 passes. A command cannot use an MCP server (Linear, for one): it is a process of its own, and the agent's authorized integrations are not its to reach. For that, give the check an instruction instead of a command: journal check create "" --set instruction="" --set every=. At its interval the journal hands the instruction to you as a turn; do it with whatever you can reach, then answer with journal check pass (--note "") or journal check fail "". A failure is filed and told like any other. A failing run files a notification and tells you; the next pass clears it. A check may also write a report to the file named by $JOURNAL_REPORT: {"title": ..., "summary": ..., "findings": [{"name", "file", "line", "where", "text", "group"}]}. The viewer shows its findings under the check, grouped, each opening its file at its line. While you iterate, journal check touched runs only the tests beside what changed since the last commit, through the check's touched command (--set touched=""), and names what no test covers. To commit, journal check gate "" --paths , runs the whole check in the background and commits exactly those paths on a pass, then runs the check's then command (--set then=""); you are told either way, so there is no log to read. Its lines and guards are for the main agent only; none reach a subagent.