Get orkai

Workflows and review

Change the Fullstack Developer workflow so a passing lint and build commits, and the git hook has to review the work.

You will learn

  • Why you change a starter-pack workflow instead of living with it as-is
  • How auto-commit after lint and build forces the git hook to review the work
  • Why that makes background orkai work safe later

The idea

The starter pack is a start, not a cage. Fullstack Developer today creates a branch, implements, verifies, and commits only when you ask. That is polite in a chat. It is weak once you have a hook.

You want the opposite of skipping review. After lint and build pass, commit. The hook runs orkai review. If review fails, the commit does not land. The agent reads the report, fixes, commits again. Never --no-verify.

Change the workflow in orkai with confidence. The next chat, and later orkai work, will follow the new steps. Background OpenCode is then safe: it commits, the hook catches the miss, it fixes. You are not babysitting every land.

How workflows work: Workflows.

Do this in OpenCode

  1. Start a new chat in the Stall folder. AGENTS.md loads overview.
  2. Paste the update prompt. It should load Fullstack Developer and save the changed close step.
  3. Open the orkai window. Workflows. Read Fullstack Developer. The close step should commit after lint and build, not wait for you to ask.
  4. Save the session. Always.

Update Fullstack Developer

Get the Fullstack Developer workflow.

Update the close step: after lint and build pass, commit. Do not wait for me to ask. The git hook must run orkai review. If review fails, do not skip the hook. Fix the findings, then commit again.

Save the workflow in orkai.

Read it in orkai

Run orkai open if the window is not already open. Select Stall. Open Workflows. This is the same habit as Documents and Project Manager: you read what was saved. 

orkai open

Why this matters for orkai work

Next lesson, unrelated tasks run in the background. Those workers follow this workflow. If it auto-commits, every land hits the hook. Review errors come back to OpenCode. It fixes them. That is the point of Protect: parallel work does not mean unprotected work.

Save the session

Save the session, I will continue in a new one.

Recap

You changed a starter-pack workflow on purpose. Commits now have to pass orkai review. Next, unrelated work can run in parallel without rewriting catalog math, and without skipping the door.