Expand description
speccoder init: detect a project’s checks and write
speccoder.toml.
Detection looks only at the project root’s manifests and lockfiles (and
whether cargo nextest is installed); it runs nothing of the project’s.
What it finds becomes a commented file the person reviews and commits.
The result is parsed back with speccoder’s own parsers before it is
written, so init never leaves a file run would refuse.
Structs§
- Found
- What
initsaw at the project root. - Prepared
initwritten and its checks run on the untouched code: what a person then decides to commit.- Preview
- What
initwould write here, without writing: for the setup assistant. - Proposed
- One check
initproposes.
Constants§
- COMMITTABLE
- The files
initmay commit: nothing else, whatever a caller asks. - NEXTEST_
PROFILE - The nextest profile speccoder’s JUnit report path expects.
Functions§
- allow
- Commands the model (and the spec-derived acceptance tests) need besides
the checks: narrow prefixes per toolchain, written to
[commands] allow. - commit_
written - Commits exactly
paths— each one ofCOMMITTABLE— asspeccoder: config; the short id. - detect
- Looks at
root(and whethercargo nextestruns). - finish
- The result of an
initthe person has decided about: the message, the report, and what comes next. - formatter
- The formatter speccoder runs after each attempt, when the toolchain has one.
- init
init_withfor this machine.- init_
with speccoder init [--provider] [--model] [--force]with an explicit view of the environment and of what is installed.- prepare
- Writes the configuration and (unless
no_verify) runs its checks on the untouched code. A refusal comes back asErr. - preview
Previewofpath.- propose
- The checks for what was found (pure: no IO).
- render
- The file
initwrites. - root_of
- Where
initwrites forpath: the spec project’s root, elsepath. - verify_
written - Runs the fast-tier checks of the configuration
initjust wrote on the untouched code, confined like in a run.