v0.8.0
One skill now serves both Codex CLI and opencode, published once to the directory they already share.
A setup skill lets you ask an agent to install semlf instead of doing it by hand.
Added
-
One skill, read by both Codex CLI and opencode.
semlf installpublishes thesemantic-linefeedsskill once, into~/.agents/skills,
and both agents load it from there — no second copy, and no per-agent copy to keep in step.
opencode had none at all before this release:
it got the checker and the plugin, and its hook then told the model to go read a skill nobody had installed for it.
It now acts on the same advice Codex does:
whichandis a real clause boundary, what never to break, and when to stop and ask you.
opencode 1.18.18 or newer is needed to see it,
and settingOPENCODE_DISABLE_EXTERNAL_SKILLShides it from opencode entirely. -
A setup skill, so you can just ask your agent to install
semlf.
Ask Claude Code, Codex CLI, or opencode to "install semlf",
and it now follows a fixed procedure instead of guessing at package names or editing your config by hand.
It installs the CLI if it is missing, repairs an install that went stale after an upgrade,
and offers to write the project's.semlf.ini.
It shows you every command before running it,
and it will not overwrite one of your files or add anexcludeline on its own —
it shows you the difference and asks. -
/setup-semlfin opencode.
opencode offers skills to the model and commands to you,
so the same procedure is installed both ways and you can start it yourself by typing the command.
Changed
- Installing for opencode alone now also writes the checker and the README to the shared install location.
They used to arrive there only when you installed for Codex CLI;
installing for opencode alone put a second checker beside its plugin instead.
The skill points at both, sosemlf install opencodewrites them even on a machine that never had Codex CLI. - The skill is removed only when you ask for both agents by name.
One copy now serves both agents, so uninstalling one of them leaves it in place for the other.
semlf uninstall codex opencodeis what takes it,
and nothing else does — including on a machine where you only ever used one of them.
That is deliberate:semlfcannot always see a Codex you installed somewhere unusual,
and it would rather leave you a file you can delete than delete one you were still using.
The checker and the README are always kept, as before,
andsemlf statusnow lists the skills too when no agent is left to read them. semlf doctornow looks inside opencode's own skills folder.
A skill file sitting there usually wins over the shared one,
so opencode would quietly answer with it instead.
doctornames the file rather than passing the machine as healthy.- A skill file you put in opencode's skills folder yourself is now refused, not replaced.
The old by-hand instructions told you to copy the skill into~/.config/opencode/skills/.
That copy competes with the one shared skill, sosemlf install opencodewants it gone —
butsemlfcannot tell your file from one it wrote, and it will not delete a file it cannot account for.
It stops and names the path instead of touching it.
If you set opencode up by hand, this is the first thing you will hit rather than a corner case:
move that file aside, then runsemlf install opencodeagain.