Code-test-review

The code-test-review workflow guides you through writing code, covering it with tests, reviewing it for issues, and shipping a pull request — as one continuous flow.

How to start it

Describe the feature or change you want to work on:

"Build the user authentication service, write tests for every decision point, and open a pull request when it's done."

"I've written the payment module — help me test it and then review the code before we open a PR."

Slo adapts to wherever you are in the process. You can start from scratch or hand off mid-way.

What happens

Step 1 — Write code

Slo loads the applicable coding skills for your stack and writes the implementation. For a FastAPI service this might include build-routers, build-domain-features, named-arguments-and-type-hints, and declarative-method-structure — all applied automatically.

You don't need to name the skills. Slo picks them based on what the code is doing.

Step 2 — Identify decision points and write tests

After writing, Slo scans the code for every decision point — every if, early return, try/except, or conditional branch. It writes one test per path, names tests after what they exercise, and runs them to make sure they pass.

"Test files 4 passed (4) — Tests 12 passed (12)"

If tests fail, Slo fixes the code (or the test) before moving on.

Step 3 — Code review

Slo reviews the finished implementation against:

  • The applicable build skills for the stack (router conventions, docstrings, named args, etc.)
  • Security — OWASP top 10, injection, XSS, CSRF, secrets in code
  • The ubiquitous language convention — names must be consistent across every layer
  • The test verification policy — every decision point must have a test

You can ask for a lighter-touch review ("just check for obvious bugs") or a thorough audit ("review everything").

Step 4 — Ship the PR

Slo creates a branch, writes a commit message, pushes, and opens a pull request with a full summary of what changed and why.

Tips

  • If you want to review mid-build: "Stop here and review what we have so far."
  • If you only want the review step: "Review my current code changes."
  • If you want to skip straight to the PR: "Open a PR for this branch."

Each step is independently available — you can ask for just the part you need.