opencode-kolchoz-loop 1.0.5 → 1.3.1

package/README.md

@@ -122,19 +122,25 @@ The plugin registers 7 tools:
 
 ## Model configuration
 
-Agents use `claude-sonnet-4` by default. Override in `opencode.json`:
+You can override agent models in `opencode.json`:
 
 ```json
 {
   "agent": {
-    "januszek": { "model": "anthropic/claude-opus-4-20250514" },
-    "areczek": { "model": "openai/gpt-4.1" },
-    "anetka": { "model": "google/gemini-2.5-pro" }
+    "januszek": { "model": "<provider>/<model-name>" },
+    "areczek": { "model": "<provider>/<model-name>" },
+    "anetka": { "model": "<provider>/<model-name>" }
   }
 }
 ```
 
-Recommendation: Anetka and Areczek should use different models. Cross-model review reduces shared blind spots.
+## Commit gate
+
+Before Areczek can submit a story for review, `kolchoz_submit_for_review` validates Git:
+- no uncommitted changes in the working tree
+- latest commit message starts with `feat(<storyId>):`
+
+If either check fails, submission is blocked until Areczek creates the correct commit.
 
 ## Compound engineering
 
@@ -144,6 +150,28 @@ The system builds knowledge in `AGENTS.md` automatically:
 2. Anetka discovers a gotcha -> `kolchoz_learn("gotcha", "...")`
 3. Future sessions read AGENTS.md -> better context -> better outcomes
 
+## Release automation
+
+This repository includes GitHub Actions workflows for a release cycle:
+
+1. Run `Prepare Release Draft` manually from GitHub Actions on `main` or `master`.
+2. Choose `RELEASE_TYPE`: `major`, `minor`, or `patch`.
+3. Workflow bumps `package.json` version, commits it, creates a tag, and opens a draft release.
+4. Publish the draft release in GitHub Releases.
+5. Publishing the release triggers npm publishing from the release tag.
+
+Workflow files:
+- `.github/workflows/prepare-release.yml`
+- `.github/workflows/publish-on-release.yml`
+
+Required npm setup:
+- Configure npm Trusted Publisher for this GitHub repository and workflow file `publish-on-release.yml`.
+- Trusted publishing uses GitHub OIDC, so `NPM_TOKEN` is not required for package publishing.
+
+Important:
+- `Prepare Release Draft` guarantees matching `tag` and `package.json` version.
+- If branch protection blocks direct pushes by Actions, allow `GITHUB_TOKEN` pushes for this workflow.
+
 ## License
 
 MIT

package/dist/agents/agents/areczek.md

@@ -41,6 +41,9 @@ Use these capabilities consistently:
 - Commit format: `feat(story-id): short description`
 - Always inspect `git diff` before committing
 - If something goes wrong: `git stash` or `git reset`
+- `kolchoz_submit_for_review` is hard-gated by Git checks:
+  - working tree must be clean (no pending changes)
+  - latest commit message must match current story: `feat(<storyId>): ...`
 
 ### Tests
 - Run existing tests after changes: `npm test` / `bun test` / equivalent

package/dist/agents/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules
 

package/dist/agents/areczek.md

@@ -41,6 +41,9 @@ Use these capabilities consistently:
 - Commit format: `feat(story-id): short description`
 - Always inspect `git diff` before committing
 - If something goes wrong: `git stash` or `git reset`
+- `kolchoz_submit_for_review` is hard-gated by Git checks:
+  - working tree must be clean (no pending changes)
+  - latest commit message must match current story: `feat(<storyId>): ...`
 
 ### Tests
 - Run existing tests after changes: `npm test` / `bun test` / equivalent

package/dist/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules
 

package/dist/index.js

@@ -2,6 +2,9 @@ import { tool } from "@opencode-ai/plugin/tool";
 import { readFile, writeFile, mkdir, readdir, copyFile, stat } from "fs/promises";
 import { join, dirname } from "path";
 import { fileURLToPath } from "url";
+import { execFile } from "child_process";
+import { promisify } from "util";
+const execFileAsync = promisify(execFile);
 // ── Filesystem helpers ──
 async function ensureDir(dir) {
     await mkdir(dir, { recursive: true });
@@ -41,6 +44,30 @@ async function appendProgress(dir, message) {
         await writeFile(file, line, "utf-8");
     }
 }
+async function runGit(projectRoot, args) {
+    const { stdout } = await execFileAsync("git", args, { cwd: projectRoot });
+    return stdout.trim();
+}
+async function validateStoryCommit(projectRoot, storyId) {
+    try {
+        await runGit(projectRoot, ["rev-parse", "--is-inside-work-tree"]);
+    }
+    catch {
+        return "ERROR: Git repository not found. Commit is required before review.";
+    }
+    const status = await runGit(projectRoot, ["status", "--porcelain"]);
+    if (status.length > 0) {
+        return (`ERROR: Uncommitted changes detected. Commit all changes for ${storyId} before review.\n` +
+            `Hint: git add -A && git commit -m "feat(${storyId}): short description"`);
+    }
+    const lastCommitMessage = await runGit(projectRoot, ["log", "-1", "--pretty=%s"]);
+    const requiredPrefix = `feat(${storyId}):`;
+    if (!lastCommitMessage.startsWith(requiredPrefix)) {
+        return (`ERROR: Last commit message must start with "${requiredPrefix}".\n` +
+            `Current: "${lastCommitMessage}"`);
+    }
+    return null;
+}
 // ── Agent provisioning ──
 // Copies bundled .md agent files to .opencode/agents/
 // so OpenCode discovers them as real agents.
@@ -89,6 +116,16 @@ async function ensureGitignore(projectRoot) {
 // ── Main Plugin Export ──
 export const KolchozLoop = async ({ project, client, $, directory, worktree }) => {
     const projectRoot = worktree || directory;
+    if (!projectRoot || projectRoot === "/") {
+        await client.app.log({
+            body: {
+                service: "kolchoz-loop",
+                level: "warn",
+                message: `Kolchoz Loop: no valid project directory (worktree="${worktree}", directory="${directory}"). Plugin inactive.`,
+            },
+        });
+        return { tool: {}, event: async () => { } };
+    }
     const stateDir = join(projectRoot, ".opencode", "state");
     // ── Auto-provision on first run ──
     await ensureDir(stateDir);
@@ -121,16 +158,29 @@ export const KolchozLoop = async ({ project, client, $, directory, worktree }) =
                     stories: tool.schema.string(), // JSON array
                 },
                 async execute(args) {
-                    const stories = JSON.parse(args.stories).map((s, i) => ({
-                        id: s.id || `story-${i + 1}`,
-                        title: s.title || `Story ${i + 1}`,
-                        description: s.description || "",
-                        acceptanceCriteria: s.acceptanceCriteria || [],
-                        priority: s.priority || "medium",
-                        status: "pending",
-                        assignedTo: "areczek",
-                        iteration: 0,
-                    }));
+                    let parsed;
+                    try {
+                        const raw = JSON.parse(args.stories);
+                        if (!Array.isArray(raw))
+                            throw new Error("stories must be a JSON array");
+                        parsed = raw;
+                    }
+                    catch (err) {
+                        return `ERROR: Invalid stories JSON — ${err instanceof Error ? err.message : String(err)}`;
+                    }
+                    const stories = parsed.map((value, i) => {
+                        const s = value;
+                        return {
+                            id: s.id || `story-${i + 1}`,
+                            title: s.title || `Story ${i + 1}`,
+                            description: s.description || "",
+                            acceptanceCriteria: s.acceptanceCriteria || [],
+                            priority: s.priority || "medium",
+                            status: "pending",
+                            assignedTo: "areczek",
+                            iteration: 0,
+                        };
+                    });
                     const prd = {
                         title: args.title,
                         createdBy: "grazynka",
@@ -202,6 +252,11 @@ export const KolchozLoop = async ({ project, client, $, directory, worktree }) =
                     const story = prd.userStories.find((s) => s.id === args.storyId);
                     if (!story)
                         return `ERROR: Story ${args.storyId} not found.`;
+                    const commitValidationError = await validateStoryCommit(projectRoot, args.storyId);
+                    if (commitValidationError) {
+                        await appendProgress(stateDir, `[Areczek] Submission blocked for ${args.storyId}: missing/invalid commit`);
+                        return commitValidationError;
+                    }
                     story.status = "review";
                     await writeJson(stateDir, "prd.json", prd);
                     const state = await readJson(stateDir, "loop-state.json", {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-kolchoz-loop",
-  "version": "1.0.5",
+  "version": "1.3.1",
   "description": "Multi-agent Ralph Loop plugin for OpenCode - Januszek, Grazynka, Areczek, Anetka",
   "type": "module",
   "main": "./dist/index.js",
@@ -27,11 +27,11 @@
     "access": "public"
   },
   "dependencies": {
-    "@opencode-ai/plugin": "latest"
+    "@opencode-ai/plugin": "^1.2.7"
   },
   "devDependencies": {
-    "@types/node": "latest",
-    "typescript": "latest"
+    "@types/node": "^25.3.0",
+    "typescript": "^5.9.3"
   },
   "files": [
     "dist/**/*",

package/src/agents/areczek.md

@@ -41,6 +41,9 @@ Use these capabilities consistently:
 - Commit format: `feat(story-id): short description`
 - Always inspect `git diff` before committing
 - If something goes wrong: `git stash` or `git reset`
+- `kolchoz_submit_for_review` is hard-gated by Git checks:
+  - working tree must be clean (no pending changes)
+  - latest commit message must match current story: `feat(<storyId>): ...`
 
 ### Tests
 - Run existing tests after changes: `npm test` / `bun test` / equivalent

package/src/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules