Write code

Books matched to this capability.

5books in this track

L01 · User

Who is affectedOnly you
T08-L01

Start With OpenCode: Set It Up, Change One Line, and Undo It

Step by step, with a screenshot for every step: install OpenCode Desktop, pick a free model, have it explain a small page, change one line, see exactly what changed and take it back.

Outcome: A before-and-after table of five searches for your changed page, a screenshot of the Review panel showing the one changed line, and one sentence saying how you undid the change; it passes when all five results match, only the intended line changed, and Undo brought the old behaviour back.

User17 minLast edited: Oct 18, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T08-L02

Get a Script Your Colleague Can Rerun, Without Being a Developer

Turn a monthly spreadsheet chore into a small Python script with OpenCode Desktop, then make it something a colleague can run without you: a known-answer test worked out by hand, clear refusals for bad input, a one-page README, and a shared Git repository your team can find.

Outcome: A shared Git repository with the script, a README, a known-answer test file and its expected output; it passes when a colleague, on their own computer and using only the README, gets exactly the expected output from the test file, and gets a clear refusal with a line number from one broken row.

Power user21 minLast edited: Oct 18, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T08-L03

Write the Spec First, So an AI Assistant Can Change Code Your Team Depends On

Change a script several colleagues depend on without breaking it: write a one-page spec with numbered rules and known-answer tests before any code, let OpenCode plan and build against it, review the diff rule by rule, and have a colleague rerun every test before you release the new version.

Outcome: A repository with SPEC.md, known-answer tests, the changed script, CHANGES.md and a version tag; it passes when a colleague, on their own computer and using only the README, runs the tests and all pass, and can point to the rule in SPEC.md behind every changed block of code.

Builder29 minLast edited: Oct 18, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T08-L04

Use OpenCode Desktop on Your Organisation's Real Repositories

Set up OpenCode Desktop for work: the approved model, sharing off, and permissions that keep secrets and pushes out of the assistant's reach. Then deliver every AI-assisted change on a branch, as a pull request a second person reviews, into a protected main branch, with credentials IT issues for the job.

Outcome: One merged pull request in a real team repository, made with OpenCode, plus a one-page repository record. It passes when main rejects a direct push, a second person approved the pull request against the spec, the secret scan and tests ran before the push, and the record names the account, its access and the undo.

Integrator27 minLast edited: Oct 18, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T08-L05

Run Automatic Checks, an AI Reviewer and Releases You Can Roll Back

Keep code that many colleagues depend on safe to change for months: checks that run on every pull request, an AI reviewer that can only comment, a rule for every new package, releases the server runs by version, a tested rollback, a weekly look at the numbers, and a deputy who can run it all.

Outcome: A repository with required checks, a comment-only AI reviewer, dependency notes, a release record and a runbook, plus a handover record. It passes when a pull request that breaks a known answer is blocked, a rollback drill restores the previous version in under 15 minutes, and the deputy runs both without help.

Operator34 minLast edited: Oct 18, 2026