redline

Read one Text Artifact against the editorial contract, repair what the review found within the budget the invocation allows, say what is left, and close with one mechanical pass. The artifact may come from anywhere: this collection wrote it, a person wrote it, or something else produced it entirely.

Run UV_NO_CACHE=1 UV_NO_PROJECT=1 uv run "$HERE/scripts/invoke.py" — $HERE is the directory that holds this SKILL.md — with everything the user typed after /redline, verbatim and however many lines, on stdin. Exit 0: do what it prints. On any other exit, if you introduced a known construction error and can correct it while preserving the user's request and authority, account for effects already produced, submit the corrected invocation through the same shim, and continue from the failed boundary; a refusal before the operation starts consumes no operation. Otherwise show what it printed to the user verbatim and stop. Never repair input the user supplied, or automatically retry exact help, an unmet dependency, an unrelated failure, or a failure whose origin or valid correction is unknown.

Run every UV command in this Skill with a fresh private directory as TMPDIR, and remove that directory after the command, including when it fails. The private directory belongs to that one command and no other run, so cleanup removes only files this run created.

Name every private directory this run makes, for a UV command or for its own working files, by its full path, and never make one the shell's working directory. A Harness may keep a cd from one command to the next and then hold the removal of the directory the shell stands in for an approval nobody may be there to give, so a run that entered its own directory cannot remove it and leaves its working files behind. Where the shell stands in one anyway, leave it in a command of its own before removing the directory. A removal the Harness refuses or holds for approval is not tried again in another form or with another tool: the files stay where they are, and the reply names each of them by its path.

Arguments

The operand is the Text Artifact: inline text, one local path, or one URL, and exactly one of them — several paths, a glob reaching more than one file, or a directory of texts is more than one. Where the invocation carries no operand, it is the single text the current turn identifies.

--genre=<genre> names a resource under $LIBRARY/references/editorial/genres/, by its filename without the extension.

--technique=<technique> names a resource under $LIBRARY/references/editorial/techniques/, the same way.

--language=<language> names the language or locale whose editorial guidance applies. Any spelling the Collection's resolver reaches is accepted — a canonical code (sv, en_GB), a case or separator variant of one (en-GB, EN_GB), a curated alias (BrE, brittisk engelska), or an ordinary description of a language in any language.