Files
pipelines/examples/review.md
T
alan e37b864c40 stage turns: replace JSON results with file-based markdown turns
Each model visit now gets <run>/stages/<seq>-<stage>/ with input.md,
memory.md, output.md, private/ and a shared run-level public/. The model
reads the two input files, follows the stage's instructions verbatim and
returns complete markdown; only the # outcome section is parsed.

- add internal/turn layout, render and output parsing
- write input.md/memory.md before a visit and output.md from the final
  message; inventory all turn files as stage artifacts
- accumulate completed turns and system-written public file additions in
  memory, including across retries and resume
- remove the JSON envelope, strict field validation, line format and the
  repair ladder for model stages
- republish pipeline authoring prompts and docs in the new style

Checks: go build ./..., go vet ./..., go test -count=1 ./..., gofmt -l .
2026-10-19 22:27:44 +01:00

1.7 KiB

stage review

Review the repository content described by the task in input.md. Read relevant files; do
not modify them or run commands. Focus on maintainability, duplication and
near-duplicate implementations, standards/library and version usage, and
consistency with repository conventions. As visible in source, assess root-cause
handling versus workarounds or shortcuts, unnecessary custom implementations,
complexity and coupling, appropriate reusable boundaries, and meaningful tests and
docs. Support each finding with a file path, specific evidence, severity and a
remedy; distinguish legitimate compatibility exceptions and nonblocking
personal-style nits from blockers. Prioritize correctness, clarity, consistency,
and the user's criteria without assuming a language or framework. Use
websearch/webfetch only when an official standard or documentation check is
needed, and record source dates/versions. Separate observed issues from
hypotheses. State explicitly that no commands were run and that runtime behavior
and checks are not tested; source inspection is not proof of execution. Return
success when the review is complete, even if it finds issues; return blocked if
the requested content or required official evidence cannot be obtained rather than
fabricating it. Do not claim issues have been fixed. Return the complete output.md markdown; the only required section is `# outcome` followed by a declared edge word, with free-form headings for the facts later stages need.
read
glob
grep
websearch
webfetch
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> #success
blocked -> #failure
error -> #failure