Review and git hooks

Point orkai review at the Stall standards already in orkai. A git hook runs it. A bad commit does not land.

The idea

OpenCode writes the shop. You still own the house rules. Those rules already live in orkai (integer cents, sold-out cannot be ordered). Review reads those standards. You do not copy them into markdown files in the repo so a hook can run.

The hook is the rule at the door: orkai review on commit. Flags and modes: Review.

Do this in OpenCode

1. Start a new chat in the Stall folder. AGENTS.md loads overview.
2. Open the orkai window. Setup page, Review. Configure the provider and the model. Create the project skipped this on purpose.
3. In the Stall folder, run orkai review init. That extends .orkai.yaml with a review block.
4. Paste the Orkai Help prompt. The Architect should point knowledge_base.documents at the Stall standard ids in orkai, and install a git hook that runs orkai review.
5. You try a bad change (a float price, or ordering sold-out soup). The hook or orkai review should fail. Revert. A good commit should pass.
6. Save the session. Always.

Review provider in orkai

Run orkai open if the window is not already open. Open Setup, then Review. Add a provider and a model. This is the chat model that reads your standards. Embeddings (from Create the project) are not this.

For this tutorial we recommend DeepSeek V4. GLM 5.3 and OpenAI Luna also work. Pick one chat model, save it, and use it for review. Do not reuse the Voyage embedding key here.

orkai open

Extend .orkai.yaml

Stall does not have a review block yet. Setup only registered the chat provider on this computer. The project file still needs a review: section. Do not write that yaml by hand. In the Stall folder, not in the orkai window, run:

orkai review init

Orkai Help and the Architect

Orkai Help is product how-to (connected at orkai init). The Architect already knows Stall. Together they should configure review against orkai standards, not new files under standards/.

Load the Orkai Help workflow. Work with the Architect to configure orkai review for this project.

Use the Stall standards already saved in orkai. Do not copy those standards into local files.

Create a git hook that protects commits. The hook must run orkai review. If review fails, the commit must not land.

Done looks like this

.orkai.yaml has a review process whose documents are the Stall standard ids. A git hook runs orkai review. A float price fails. After you revert, the commit lands. The standards did not get copied out of orkai, and they did not get “improved” away.

Save the session

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

Recap

Implementation is delegated. Responsibility is not. Review uses the same standards you already saved. Next we change the Fullstack Developer workflow so a commit has to pass that hook.