@iloom/cli 0.5.5 → 0.6.1

package/README.md

@@ -120,7 +120,7 @@ Each loom is a fully isolated container for your work:
     
 *   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
-*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`.
+*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
 *   **Unique Runtime:**
     
@@ -144,6 +144,10 @@ Command Reference
 | `il spin` |  | Launch Claude inside the current loom with context auto-detected. |
 | `il open` | `run` | Open loom in browser (web) or run your CLI tool. |
 | `il dev-server` | `dev` | Start dev server in foreground for a workspace. |
+| `il build` |  | Run the build script for a workspace. |
+| `il lint` |  | Run the lint script for a workspace. |
+| `il test` |  | Run the test script for a workspace. |
+| `il compile` | `typecheck` | Run the compile or typecheck script for a workspace. |
 | `il add-issue` | `a` | Create and AI-enhance a new issue without starting work yet. |
 | `il init` | `config` | Interactive configuration wizard. |
 | `il feedback` | `f` | Submit bug reports/feedback directly from the CLI. |
@@ -232,6 +236,73 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
+### Multi-Language/Framework Project Support
+
+iloom supports projects in any programming language through `.iloom/package.iloom.json`. This file defines scripts using raw shell commands instead of npm scripts.
+
+**File Location:** `.iloom/package.iloom.json`
+
+**Format:**
+```json
+{
+  "scripts": {
+    "install": "bundle install",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run",
+    "lint": "cargo clippy",
+    "typecheck": "cargo check"
+  }
+}
+```
+
+**Supported Scripts:**
+
+| Script | Purpose | When Used |
+|--------|---------|-----------|
+| `install` | Install dependencies | `il start` (loom creation), `il finish` (post-merge) |
+| `build` | Compile/build project | `il build`, `il finish` (CLI projects, post-merge) |
+| `test` | Run test suite | `il test`, `il finish` validation |
+| `dev` | Start dev server | `il dev-server` |
+| `lint` | Run linter | `il lint`, `il finish` validation |
+| `typecheck` | Type checking | `il typecheck`, `il finish` validation |
+| `compile` | Alternative to typecheck | `il compile`, `il finish` validation (preferred over typecheck if both exist) |
+
+All scripts are optional. If not defined, that step is skipped.
+
+**Language Examples:**
+
+| Language | Install | Build | Test | Dev | Lint | Typecheck |
+|----------|---------|-------|------|-----|------|-----------|
+| Rust | `cargo fetch` | `cargo build` | `cargo test` | `cargo run` | `cargo clippy` | `cargo check` |
+| Python (pip) | `pip install -e .` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Python (poetry) | `poetry install` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Ruby | `bundle install` | - | `bundle exec rspec` | `rails server` | `bundle exec rubocop` | - |
+| Go | `go mod download` | `go build ./...` | `go test ./...` | `go run .` | `golangci-lint run` | `go vet ./...` |
+
+**Precedence Rules:**
+1. `.iloom/package.iloom.json` (if exists) - highest priority
+2. `package.json` (if exists) - fallback for Node.js projects
+
+**Key Differences from package.json:**
+- Scripts are raw shell commands, executed directly (not via npm/pnpm)
+- No package manager prefix is added to commands
+- Works with any language's toolchain
+
+**Automatic Detection:** When running `il init` on a non-Node.js project, iloom will offer to detect your project's language and generate an appropriate `package.iloom.json`.
+
+**→ [Complete Multi-Language Project Guide](docs/multi-language-projects.md)** - Detailed setup instructions, more language examples, and troubleshooting.
+
+**Secret Storage Limitations:** iloom manages environment variables through standard `.env` files (via dotenv-flow). The following encrypted/proprietary secret storage formats are **not supported**:
+
+| Format | Why Unsupported |
+|--------|-----------------|
+| Rails encrypted credentials (`config/credentials.yml.enc`) | Requires Rails internals + master key |
+| ASP.NET Core User Secrets | Stored outside project at `~/.microsoft/usersecrets/<guid>/` |
+| SOPS/Sealed Secrets | Requires external decryption keys |
+
+**Recommendation:** If you want to use database isolation features (or anything else that requires updating env variables), use standard `.env` files for iloom compatibility. For Rails, consider [dotenv-rails](https://github.com/bkeepers/dotenv). For ASP.NET, use a local `.env` file alongside User Secrets.
+
 ### Copying Gitignored Files to Looms
 
 By default, looms only contain files tracked by Git. If you have local files that are gitignored (like SQLite databases, test data, or sensitive configuration), they won't be available in your looms.
@@ -291,6 +362,18 @@ Control how `il finish` handles your work. Configure in `.iloom/settings.json`:
 | `github-pr` | Push branch and create a GitHub PR on `il finish`. Worktree cleanup is optional. |
 | `github-draft-pr` | Create a draft PR immediately on `il start`. On `il finish`, the PR is marked ready for review. **Recommended for contributions to forked repos.** |
 
+### Rebase Conflict Resolution
+
+When `il finish` or `il rebase` encounter rebase conflicts, iloom automatically launches Claude to help resolve them. During conflict resolution, the following git commands are **auto-approved** so Claude can work efficiently without requiring manual permission for each command:
+
+- `git status` - View current rebase state
+- `git diff` - Examine conflicts
+- `git log` - Understand branch history
+- `git add` - Stage resolved files
+- `git rebase` - Continue or abort rebase
+
+Note: Potentially destructive commands like `git reset` and `git checkout` are intentionally not auto-approved to prevent accidental data loss.
+
 **When to use `github-draft-pr`:**
 - **Contributing to forks:** When you don't are contributing to a forked repo use this mode to create the PR from your fork immediately, allowing iloom's agents to post workflow comments directly to the PR instead of writing to the upstream repo's issues (which may not be appreciated by the repo owners).
 - CI runs on your branch during development (draft PRs trigger CI on most repos)
@@ -380,10 +463,10 @@ This is an early-stage product.
 **Project Support:**
 
 *   ✅ **Node.js Web Projects:** First-class support via package.json scripts (dev, test, build).
-    
+
 *   ✅ **Node.js CLI Tools:** Full support with isolated binary generation.
-    
-*   ⚠️ **Other Stacks:** Python/Go/Rust etc. can work via generic package.json scripts, but are not natively supported yet.    
+
+*   ✅ **Multi-Language Projects:** Python, Rust, Ruby, Go, and other languages via `.iloom/package.iloom.json`.    
 
 See all [known limitations](https://github.com/iloom-ai/iloom-cli/issues?q=is:issue+is:open+label:known-limitation) on GitHub. If you're feeling left out - you're absolutely right! The best way to complain about something is to fix it. So...
 
@@ -396,6 +479,19 @@ We (Claude and I) welcome contributions! We've made it easy to get started — i
 iloom contribute   # Handles forking, cloning, and setting up the dev environment automatically.
 ```
 
+You can also use `iloom contribute` to set up any GitHub repository for contribution:
+
+```bash
+# Full URL format
+iloom contribute "https://github.com/n8n-io/n8n"
+
+# Shortened URL format
+iloom contribute "github.com/n8n-io/n8n"
+
+# owner/repo format
+iloom contribute "n8n-io/n8n"
+```
+
 **All PRs should be created with iloom or include detailed context.** When you run `iloom contribute`, it configures iloom to create a draft PR as soon as you start work. As you work, iloom posts the AI's analysis, implementation plan, and progress directly to that draft PR—giving reviewers full context before the code is even ready for review. If you're not using iloom, please provide equivalent detail in your PR.
 
 New contributors should start with issues labeled [starter-task](https://github.com/iloom-ai/iloom-cli/issues?q=is%3Aissue+is%3Aopen+label%3Astarter-task). For details, see our [Contributing Guide](CONTRIBUTING.md).

package/dist/{ClaudeContextManager-7WX7DUNI.js → ClaudeContextManager-6J2EB4QU.js}

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 import {
   ClaudeContextManager
-} from "./chunk-VXMY22TP.js";
-import "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-7WANFUIK.js";
+import "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import "./chunk-F6WVM437.js";
 import "./chunk-AEIMYF4P.js";
 import "./chunk-6MLEBAYZ.js";
@@ -11,4 +11,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   ClaudeContextManager
 };
-//# sourceMappingURL=ClaudeContextManager-7WX7DUNI.js.map
+//# sourceMappingURL=ClaudeContextManager-6J2EB4QU.js.map

package/dist/{ClaudeService-LQLN2GP4.js → ClaudeService-O2PB22GX.js}

@@ -1,8 +1,8 @@
 #!/usr/bin/env node
 import {
   ClaudeService
-} from "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import "./chunk-F6WVM437.js";
 import "./chunk-AEIMYF4P.js";
 import "./chunk-6MLEBAYZ.js";
@@ -10,4 +10,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   ClaudeService
 };
-//# sourceMappingURL=ClaudeService-LQLN2GP4.js.map
+//# sourceMappingURL=ClaudeService-O2PB22GX.js.map

package/dist/{LoomLauncher-5QU42LOM.js → LoomLauncher-5LFM4LXB.js}

@@ -4,9 +4,9 @@ import {
 } from "./chunk-O7VL5N6S.js";
 import {
   ClaudeContextManager
-} from "./chunk-VXMY22TP.js";
-import "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-7WANFUIK.js";
+import "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import {
   getExecutablePath
 } from "./chunk-GYCR2LOU.js";
@@ -252,4 +252,4 @@ var LoomLauncher = class {
 export {
   LoomLauncher
 };
-//# sourceMappingURL=LoomLauncher-5QU42LOM.js.map
+//# sourceMappingURL=LoomLauncher-5LFM4LXB.js.map

package/dist/{PRManager-OCSB2HPT.js → PRManager-GB3FOJ2W.js}

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   PRManager
-} from "./chunk-5IWU3HXE.js";
+} from "./chunk-VDA5JMB4.js";
 import "./chunk-YETJNRQM.js";
 import "./chunk-FXDYIV3K.js";
 import "./chunk-LT3SGBR7.js";
@@ -11,4 +11,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   PRManager
 };
-//# sourceMappingURL=PRManager-OCSB2HPT.js.map
+//# sourceMappingURL=PRManager-GB3FOJ2W.js.map

package/dist/ProjectCapabilityDetector-S5FLNCFI.js

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+import {
+  ProjectCapabilityDetector
+} from "./chunk-ZPSTA5PR.js";
+import "./chunk-BXCPJJYM.js";
+import "./chunk-6MLEBAYZ.js";
+import "./chunk-VT4PDUYT.js";
+export {
+  ProjectCapabilityDetector
+};
+//# sourceMappingURL=ProjectCapabilityDetector-S5FLNCFI.js.map

package/dist/{PromptTemplateManager-5GNF7FCP.js → PromptTemplateManager-C3DK6XZL.js}

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 import {
   PromptTemplateManager
-} from "./chunk-K5G5SFWY.js";
+} from "./chunk-W6WVRHJ6.js";
 import "./chunk-VT4PDUYT.js";
 export {
   PromptTemplateManager
 };
-//# sourceMappingURL=PromptTemplateManager-5GNF7FCP.js.map
+//# sourceMappingURL=PromptTemplateManager-C3DK6XZL.js.map

package/dist/README.md

@@ -120,7 +120,7 @@ Each loom is a fully isolated container for your work:
     
 *   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
-*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`.
+*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
 *   **Unique Runtime:**
     
@@ -144,6 +144,10 @@ Command Reference
 | `il spin` |  | Launch Claude inside the current loom with context auto-detected. |
 | `il open` | `run` | Open loom in browser (web) or run your CLI tool. |
 | `il dev-server` | `dev` | Start dev server in foreground for a workspace. |
+| `il build` |  | Run the build script for a workspace. |
+| `il lint` |  | Run the lint script for a workspace. |
+| `il test` |  | Run the test script for a workspace. |
+| `il compile` | `typecheck` | Run the compile or typecheck script for a workspace. |
 | `il add-issue` | `a` | Create and AI-enhance a new issue without starting work yet. |
 | `il init` | `config` | Interactive configuration wizard. |
 | `il feedback` | `f` | Submit bug reports/feedback directly from the CLI. |
@@ -232,6 +236,73 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
+### Multi-Language/Framework Project Support
+
+iloom supports projects in any programming language through `.iloom/package.iloom.json`. This file defines scripts using raw shell commands instead of npm scripts.
+
+**File Location:** `.iloom/package.iloom.json`
+
+**Format:**
+```json
+{
+  "scripts": {
+    "install": "bundle install",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run",
+    "lint": "cargo clippy",
+    "typecheck": "cargo check"
+  }
+}
+```
+
+**Supported Scripts:**
+
+| Script | Purpose | When Used |
+|--------|---------|-----------|
+| `install` | Install dependencies | `il start` (loom creation), `il finish` (post-merge) |
+| `build` | Compile/build project | `il build`, `il finish` (CLI projects, post-merge) |
+| `test` | Run test suite | `il test`, `il finish` validation |
+| `dev` | Start dev server | `il dev-server` |
+| `lint` | Run linter | `il lint`, `il finish` validation |
+| `typecheck` | Type checking | `il typecheck`, `il finish` validation |
+| `compile` | Alternative to typecheck | `il compile`, `il finish` validation (preferred over typecheck if both exist) |
+
+All scripts are optional. If not defined, that step is skipped.
+
+**Language Examples:**
+
+| Language | Install | Build | Test | Dev | Lint | Typecheck |
+|----------|---------|-------|------|-----|------|-----------|
+| Rust | `cargo fetch` | `cargo build` | `cargo test` | `cargo run` | `cargo clippy` | `cargo check` |
+| Python (pip) | `pip install -e .` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Python (poetry) | `poetry install` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Ruby | `bundle install` | - | `bundle exec rspec` | `rails server` | `bundle exec rubocop` | - |
+| Go | `go mod download` | `go build ./...` | `go test ./...` | `go run .` | `golangci-lint run` | `go vet ./...` |
+
+**Precedence Rules:**
+1. `.iloom/package.iloom.json` (if exists) - highest priority
+2. `package.json` (if exists) - fallback for Node.js projects
+
+**Key Differences from package.json:**
+- Scripts are raw shell commands, executed directly (not via npm/pnpm)
+- No package manager prefix is added to commands
+- Works with any language's toolchain
+
+**Automatic Detection:** When running `il init` on a non-Node.js project, iloom will offer to detect your project's language and generate an appropriate `package.iloom.json`.
+
+**→ [Complete Multi-Language Project Guide](docs/multi-language-projects.md)** - Detailed setup instructions, more language examples, and troubleshooting.
+
+**Secret Storage Limitations:** iloom manages environment variables through standard `.env` files (via dotenv-flow). The following encrypted/proprietary secret storage formats are **not supported**:
+
+| Format | Why Unsupported |
+|--------|-----------------|
+| Rails encrypted credentials (`config/credentials.yml.enc`) | Requires Rails internals + master key |
+| ASP.NET Core User Secrets | Stored outside project at `~/.microsoft/usersecrets/<guid>/` |
+| SOPS/Sealed Secrets | Requires external decryption keys |
+
+**Recommendation:** If you want to use database isolation features (or anything else that requires updating env variables), use standard `.env` files for iloom compatibility. For Rails, consider [dotenv-rails](https://github.com/bkeepers/dotenv). For ASP.NET, use a local `.env` file alongside User Secrets.
+
 ### Copying Gitignored Files to Looms
 
 By default, looms only contain files tracked by Git. If you have local files that are gitignored (like SQLite databases, test data, or sensitive configuration), they won't be available in your looms.
@@ -291,6 +362,18 @@ Control how `il finish` handles your work. Configure in `.iloom/settings.json`:
 | `github-pr` | Push branch and create a GitHub PR on `il finish`. Worktree cleanup is optional. |
 | `github-draft-pr` | Create a draft PR immediately on `il start`. On `il finish`, the PR is marked ready for review. **Recommended for contributions to forked repos.** |
 
+### Rebase Conflict Resolution
+
+When `il finish` or `il rebase` encounter rebase conflicts, iloom automatically launches Claude to help resolve them. During conflict resolution, the following git commands are **auto-approved** so Claude can work efficiently without requiring manual permission for each command:
+
+- `git status` - View current rebase state
+- `git diff` - Examine conflicts
+- `git log` - Understand branch history
+- `git add` - Stage resolved files
+- `git rebase` - Continue or abort rebase
+
+Note: Potentially destructive commands like `git reset` and `git checkout` are intentionally not auto-approved to prevent accidental data loss.
+
 **When to use `github-draft-pr`:**
 - **Contributing to forks:** When you don't are contributing to a forked repo use this mode to create the PR from your fork immediately, allowing iloom's agents to post workflow comments directly to the PR instead of writing to the upstream repo's issues (which may not be appreciated by the repo owners).
 - CI runs on your branch during development (draft PRs trigger CI on most repos)
@@ -380,10 +463,10 @@ This is an early-stage product.
 **Project Support:**
 
 *   ✅ **Node.js Web Projects:** First-class support via package.json scripts (dev, test, build).
-    
+
 *   ✅ **Node.js CLI Tools:** Full support with isolated binary generation.
-    
-*   ⚠️ **Other Stacks:** Python/Go/Rust etc. can work via generic package.json scripts, but are not natively supported yet.    
+
+*   ✅ **Multi-Language Projects:** Python, Rust, Ruby, Go, and other languages via `.iloom/package.iloom.json`.    
 
 See all [known limitations](https://github.com/iloom-ai/iloom-cli/issues?q=is:issue+is:open+label:known-limitation) on GitHub. If you're feeling left out - you're absolutely right! The best way to complain about something is to fix it. So...
 
@@ -396,6 +479,19 @@ We (Claude and I) welcome contributions! We've made it easy to get started — i
 iloom contribute   # Handles forking, cloning, and setting up the dev environment automatically.
 ```
 
+You can also use `iloom contribute` to set up any GitHub repository for contribution:
+
+```bash
+# Full URL format
+iloom contribute "https://github.com/n8n-io/n8n"
+
+# Shortened URL format
+iloom contribute "github.com/n8n-io/n8n"
+
+# owner/repo format
+iloom contribute "n8n-io/n8n"
+```
+
 **All PRs should be created with iloom or include detailed context.** When you run `iloom contribute`, it configures iloom to create a draft PR as soon as you start work. As you work, iloom posts the AI's analysis, implementation plan, and progress directly to that draft PR—giving reviewers full context before the code is even ready for review. If you're not using iloom, please provide equivalent detail in your PR.
 
 New contributors should start with issues labeled [starter-task](https://github.com/iloom-ai/iloom-cli/issues?q=is%3Aissue+is%3Aopen+label%3Astarter-task). For details, see our [Contributing Guide](CONTRIBUTING.md).