Teach OpenCode Go your weekly chore once, then run it in minutes

The Stack

Steps

1. 1

   Capture the chore as a reusable command and validate the config

   Walk OpenCode through the chore once, then save it as a command in opencode.json with a template that says to work on a copy and stop before overwriting anything real. Pick a Go-plan model. CI checks the config parses, names a model, and defines a real command; running the command is fenced.

   cat > opencode.json <<'JSON'
   {
     "$schema": "https://opencode.ai/config.json",
     "model": "opencode/glm-5.2",
     "command": {
       "weekly-report": {
         "template": "Rebuild this week's report from the data folder into the standard template. Work on a copy of the files and stop before overwriting anything real.",
         "description": "The captured weekly chore: run this instead of redoing it by hand."
       }
     }
   }
   JSON
   node -e '
   const fs = require("fs");
   const c = JSON.parse(fs.readFileSync("opencode.json", "utf8"));
   function bad(m) { console.error("BAD: " + m); process.exit(1); }
   const cmds = c.command || {};
   const names = Object.keys(cmds);
   if (names.length < 1) bad("no reusable command defined");
   const first = cmds[names[0]];
   if (!first || !first.template || first.template.length < 10) bad("command has no real template");
   const model = c.model || first.model || "";
   if (!model) bad("no model set (top-level or on the command)");
   console.log("config OK: opencode.json sets model " + model + " and defines " + names.length + " reusable command(s) (" + names[0] + ")");
   '

2. 2

   Run it each week (the model step, not checked by CI)

   Subscribe to OpenCode Go, then run the command. The first few times, diff what it produced against what you would have done by hand and keep a backup. Once you trust it, a two-hour chore is a five-minute run. The chore execution is fenced.