create-claude-workspace 1.1.44 → 1.1.45

package/dist/template/.claude/agents/orchestrator.md

@@ -1,6 +1,6 @@
 ---
 name: orchestrator
-description: "Use this agent to run the autonomous development cycle. It picks tasks from TODO.md, delegates planning to architect agents, manages implementation, testing, review, and commit workflow. This is the core loop agent — called by ralph-loop or manually.\n\nExamples:\n\n<example>\nuser: \"Continue autonomous development\"\nassistant: \"I'll use the orchestrator agent to pick the next task and run the full development cycle.\"\n</example>\n\n<example>\nuser: \"Run the next development iteration\"\nassistant: \"Let me use the orchestrator agent to continue from where MEMORY.md left off.\"\n</example>"
+description: "Use this agent to run the autonomous development cycle. It picks tasks from TODO.md, delegates planning to architect agents, manages implementation, testing, review, commit, and CI pipeline monitoring. This is the core loop agent — called by ralph-loop or manually.\n\nExamples:\n\n<example>\nuser: \"Continue autonomous development\"\nassistant: \"I'll use the orchestrator agent to pick the next task and run the full development cycle.\"\n</example>\n\n<example>\nuser: \"Run the next development iteration\"\nassistant: \"Let me use the orchestrator agent to continue from where MEMORY.md left off.\"\n</example>"
 model: opus
 ---
 
@@ -89,9 +89,15 @@ At the beginning of EVERY session (including every Ralph Loop iteration):
 Before doing anything, check for unexpected state from user intervention or previous session:
 - **Worktree recovery**: Read MEMORY.md `Current Worktree`. If set, check if the worktree directory exists:
   - Worktree exists + `Current Step` is set → resume from that step (continue working in the worktree)
-  - **Crash recovery for STEP 11**: If `Current Step` contains `11`:
+  - **Crash recovery for STEP 11**: If `Current Step` contains `11 —` (exactly `11 — COMMIT`, not `11b`):
     - Check `git -C {worktree} status` for uncommitted changes. If present, the STEP 11 commit was incomplete — re-stage all task files + TODO.md + MEMORY.md in the worktree and commit.
-    - If worktree is clean, the commit succeeded. Proceed to STEP 12 (merge).
+    - If worktree is clean, the commit succeeded. Proceed to STEP 11b (CI watch) if git integration active, otherwise STEP 12.
+  - **Crash recovery for STEP 11b**: If `Current Step` contains `11b`:
+    - The push already succeeded (11b runs after push). Check if a CI pipeline is running for the branch.
+    - If pipeline is running → resume polling from STEP 11b.
+    - If pipeline passed → proceed to STEP 12.
+    - If pipeline failed → resume STEP 11b fix loop (check CI fix counter in MEMORY.md Notes if logged).
+    - If no pipeline found → proceed to STEP 12 (pipeline may have been cancelled or platform is unreachable).
   - **Crash recovery for STEP 12**: If `Current Step` contains `12`:
     - Check if the feature branch has commits ahead of main. If yes, proceed to STEP 12 (merge from main).
     - If already merged: clean up worktree and branch, clear `Current Worktree` from MEMORY.md.
@@ -488,6 +494,65 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
   3. If auth/network -> retry once, then log blocker
   4. Commit is still local and safe — do NOT reset or amend without reason
 
+**STEP 11b: CI PIPELINE WATCH** (only if git integration active AND remote push succeeded)
+- Update MEMORY.md (on main): set `Current Step: 11b — CI WATCH`
+- **Skip conditions**: no remote, no push happened, local-only mode, team workflow (team doesn't merge — CI runs on MR/PR, reviewed by humans)
+- **Wait for pipeline to start** (max 60s polling):
+  ```bash
+  # GitHub — wait for workflow run to appear, capture run ID
+  for i in $(seq 1 12); do
+    RUN_ID=$(gh run list --branch feat/{slug} --limit 1 --json databaseId --jq '.[0].databaseId' 2>/dev/null)
+    [ -n "$RUN_ID" ] && break
+    sleep 5
+  done
+
+  # GitLab — wait for pipeline to appear, capture pipeline ID
+  for i in $(seq 1 12); do
+    PIPELINE_ID=$(glab ci list --branch feat/{slug} -P 1 2>/dev/null | grep -oE '^[0-9]+' | head -1)
+    [ -n "$PIPELINE_ID" ] && break
+    sleep 5
+  done
+  ```
+- **If no pipeline found after 60s**: proceed to STEP 12 (CI may not be configured for this repo). Log in MEMORY.md Notes: "No CI pipeline detected — skipped CI watch."
+- **Poll until completion** (max 1 hour):
+  ```bash
+  # GitHub — watch specific run (blocks until done, built-in polling)
+  gh run watch "$RUN_ID" --exit-status
+
+  # GitLab — poll every 15s, max 240 iterations (1 hour)
+  for i in $(seq 1 240); do
+    STATUS=$(glab ci list --branch feat/{slug} -P 1 2>/dev/null | head -1 | grep -oE '(passed|failed|success|canceled|running|pending)' | head -1)
+    case "$STATUS" in
+      passed|success) break ;;
+      failed|canceled) break ;;
+      *) sleep 15 ;;
+    esac
+  done
+  ```
+- **If CI passes** → proceed to STEP 12
+- **If CI was canceled** → the pipeline was intentionally stopped (by a human or auto-canceled by a newer push). Do NOT treat as failure. If a newer push triggered it (from a fix attempt), restart polling for the new pipeline. Otherwise proceed to STEP 12.
+- **If CI fails** → diagnose and fix (max 3 attempts). Log CI fix attempt count in MEMORY.md Notes (e.g., `CI fix attempts: 1/3`):
+  1. **Fetch CI logs**:
+     ```bash
+     # GitHub — download failed job logs for specific run
+     gh run view "$RUN_ID" --log-failed
+
+     # GitLab — view failed job trace
+     glab ci view
+     ```
+  2. **Analyze failure**: Read the logs, identify root cause (environment diff, missing secret, flaky test, build issue, dependency problem)
+  3. **Categorize**:
+     - **Fixable in code** (test failure, build error, lint issue, missing dependency): fix in worktree, amend commit (`git -C {worktree-path} add [files] && git -C {worktree-path} commit --amend --no-edit`), force-push (`git -C {worktree-path} push --force-with-lease`), restart from "Wait for pipeline"
+     - **Config/infra issue** (missing CI secret, wrong Node version, Docker build failure): if deployment-engineer can fix (CI config change), delegate to it. Otherwise log as blocker.
+     - **Flaky/intermittent** (test passed locally but fails randomly in CI): retry the pipeline once (`gh run rerun "$RUN_ID" --failed` / trigger retry via `glab ci retry`). If it passes on retry, proceed. If it fails again, treat as fixable.
+     - **Unfixable** (requires human action — missing secrets, permissions, external service down): log in MEMORY.md Blockers, proceed to STEP 12 with local merge fallback. Return `blocked` status with details.
+  4. **After each fix attempt**: increment CI fix counter in MEMORY.md Notes. If counter reaches 3:
+     - Delegate to original architect agent: "CI pipeline failed 3 times. Failures: [list]. Local build/test passes. Suggest fix or confirm this is an environment issue."
+     - If architect provides fix → apply it (final attempt)
+     - If architect confirms environment issue → proceed to STEP 12 with local merge fallback, log blocker
+     - If still failing → proceed to STEP 12 with local merge fallback, log full details in MEMORY.md Blockers
+- **Note**: `--force-with-lease` is safe here because we own the branch and just pushed it. The MR/PR stays open and updates automatically.
+
 **STEP 12: POST-MERGE & NEXT ITEM**
 - Everything was committed in STEP 11 inside the worktree. The project root (on main) has a clean working tree (tracking changes were discarded in STEP 11).
 - **ZERO commits in this step** — all tracking was already committed in STEP 11. This step only performs git operations (merge, worktree cleanup, push) and delegates issue status updates.
@@ -497,7 +562,7 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
       ```bash
       git -C {worktree-path} push origin HEAD
       ```
-    - Merge via platform to properly close the MR/PR (if CI status checks are required, this will fail — use local merge fallback below):
+    - Merge via platform to properly close the MR/PR (CI should have passed in STEP 11b — if merge still fails due to checks, use local merge fallback below):
       ```bash
       # GitHub
       gh pr merge --merge --delete-branch
@@ -641,6 +706,8 @@ Examples:
 - Task completed: `status: completed, action: continue, message: "Implemented user auth flow and pushed MR #42", task_completed: "#42 User auth", next_task: "#43 Dashboard"`
 - Missing token: `status: needs_input, action: needs_gitlab_token, message: "git push failed — GITLAB_TOKEN is missing or expired. Please provide a valid token."`
 - Build stuck: `status: error, action: retry_after_cooldown, message: "Build failed 3 times on dependency resolution. Exhausted fix attempts."`
+- CI fixed: `status: completed, action: continue, message: "CI failed on lint — fixed and re-pushed. Task merged after CI passed.", task_completed: "#42 User auth", next_task: "#43 Dashboard"`
+- CI unfixable: `status: completed, action: ci_needs_config, message: "CI pipeline failed — missing NODE_AUTH_TOKEN secret. Task merged locally (fallback).", task_completed: "#42 User auth", next_task: "#43 Dashboard"`
 - Blocked: `status: blocked, action: needs_user_decision, message: "Task #15 requires API design decision — REST vs GraphQL. Cannot proceed without guidance."`
 
 ## Rules

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.44",
+  "version": "1.1.45",
   "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
   "type": "module",
   "bin": {
@@ -28,6 +28,10 @@
   ],
   "author": "",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://gitlab.com/LadaBr/claude-starter-kit.git"
+  },
   "devDependencies": {
     "typescript": "^5.8.0",
     "vitest": "^4.0.18"