Repository navigation
skern init prompts interactively with no non-interactive opt-out #104
Description
skern init asks:
Append skern usage instructions to agent config files (AGENTS.md, CLAUDE.md, .claude/CLAUDE.md)? [y/N]:
--instructions and --print-instructions opt in. There is no flag to opt out, so a tool that spawns skern init from an installer has to rely on the prompt defaulting to N when stdin is not a TTY. That works today but is undeclared behavior — it silently becomes a hang if the default ever changes to a blocking read.
Requested behavior: a --no-instructions flag (or a general --yes / --non-interactive) so automated callers state their intent explicitly instead of depending on stdin handling.
Definition of Done
- Explicit opt-out flag
- Documented behavior when stdin is not a TTY
Activity
devrimcavusoglu commentedon Aug 19, 2026
Implemented in #107:
skern init --no-instructions.Worth knowing: skern already never prompted when stdin is not a TTY or
--jsonis set —resolveInstructionChoicesgates onisTerminal(stdin), so there was no path to a blocking read. What was missing was the stated guarantee plus an explicit flag; both are now in--helpand the docs ("Interactivity contract").--no-instructionscombined with any opt-in flag is a validation error (exit 2).Add `skern init --no-instructions` explicit opt-out (#104)
Add `skern init --no-instructions` explicit opt-out (#104) (#110)
Cut v0.4.0: stamp CHANGELOG, bump version refs (#111)