How do I install the Lumi Lab Tests skill?

Run npx skillmds@latest add omayka-tech/lumi-lab-tests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lumi Lab Tests safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lumi Lab Tests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lumi Lab Tests free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lumi Lab Tests?

Omayka-Tech (@omayka-tech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lumi Lab Tests by omayka-tech — Agent Skill

Name: Lumi Lab Tests
Author: Omayka-Tech

Lumi Lab Tests

Runs Lumi ERP tests and git/worktree work the factory way: Docker-only pytest via official wrappers, never host Python; Fusion worktree vs runtime clone; Conventional Commits; no auto-merge. Use when coding on lumi-erp, running pytest/Vitest/e2e, cherry-picking onto main, opening PRs from Fusion/MiniMax, or when a ticket mentions worktree, dev-infra, KB-xxx, or scan_matching tests.

Omayka-Tech Updated Sep 22, 2026

File contents

Lumi lab + factory (do this first)

You are on the lumi-coder VM or in Cursor against Lumi. Read product AGENTS.md → CLAUDE.md → docs/agents/LUMI_LAB_AND_FACTORY.md before docker exec / pytest.

Two clones (never mix)

Path	Role
`/workspace/lumi-erp` + `/workspace/lumi-erp/.worktrees/<name>`	Edit here. Fusion ticket branch.
`/runtime/lumi` → host `~/lumi/lumi-erp`	Live lab bind-mounted into `lumi_backend_dev_infra` (usually `develop`)
`http://backend:8000`	Live API (docker DNS)

Edit only the Fusion worktree / /workspace/lumi-erp.
Never ./scripts/dev-infra.sh up from /workspace.
docker exec lumi_backend_dev_infra … sees runtime develop, not your worktree files.

Tests (non-negotiable)

Forbidden: pytest / python -m pytest / npx playwright / npm run test:unit on the VM host or Fusion image.

Worktree-only code:

cd /workspace/lumi-erp/.worktrees/<this-ticket>
/opt/lumi-coder/scripts/agent-lumi.sh test-worktree apps/purchases/tests/test_scan_matching_normalize.py -q --tb=short

Runtime / already-pulled develop:

./scripts/dev-infra-test.sh apps/purchases/tests/test_scan_matching_normalize.py -q --tb=short
# or: /opt/lumi-coder/scripts/agent-lumi.sh test-runtime …

Do not use docker exec --entrypoint (exec has no such flag).

Git / PR

Base main. One ticket → one PR. Conventional Commits English. Never merge. Commit before pausing (Fusion may delete the worktree and drop untracked files).

Product rules

Multi-tenant by schema. /api/v1/ only for new APIs. Layered Django+DRF. No invented fiscal rules. Research tickets ([research] / /deerflow) are docs-only.

---name: lumi-lab-testsdescription: Runs Lumi ERP tests and git/worktree work the factory way: Docker-only pytest via official wrappers, never host Python; Fusion worktree vs runtime clone; Conventional Commits; no auto-merge. Use when coding on lumi-erp, running pytest/Vitest/e2e, cherry-picking onto main, opening PRs from Fusion/MiniMax, or when a ticket mentions worktree, dev-infra, KB-xxx, or scan_matching tests.---# Lumi lab + factory (do this first)You are on the **lumi-coder VM** or in Cursor against Lumi. Read product `AGENTS.md` → `CLAUDE.md` → `docs/agents/LUMI_LAB_AND_FACTORY.md` before `docker exec` / `pytest`.## Two clones (never mix)| Path | Role ||---|---|| `/workspace/lumi-erp` + `/workspace/lumi-erp/.worktrees/<name>` | **Edit here.** Fusion ticket branch. || `/runtime/lumi` → host `~/lumi/lumi-erp` | **Live lab** bind-mounted into `lumi_backend_dev_infra` (usually `develop`) || `http://backend:8000` | Live API (docker DNS) |- Edit **only** the Fusion worktree / `/workspace/lumi-erp`.- **Never** `./scripts/dev-infra.sh up` from `/workspace`.- `docker exec lumi_backend_dev_infra …` sees **runtime `develop`**, not your worktree files.## Tests (non-negotiable)**Forbidden:** `pytest` / `python -m pytest` / `npx playwright` / `npm run test:unit` on the VM host or Fusion image.Worktree-only code:```bashcd /workspace/lumi-erp/.worktrees/<this-ticket>/opt/lumi-coder/scripts/agent-lumi.sh test-worktree apps/purchases/tests/test_scan_matching_normalize.py -q --tb=short```Runtime / already-pulled develop:```bash./scripts/dev-infra-test.sh apps/purchases/tests/test_scan_matching_normalize.py -q --tb=short# or: /opt/lumi-coder/scripts/agent-lumi.sh test-runtime …```Do **not** use `docker exec --entrypoint` (`exec` has no such flag).## Git / PRBase **`main`**. One ticket → one PR. Conventional Commits English. **Never merge.** Commit before pausing (Fusion may delete the worktree and drop untracked files).## Product rulesMulti-tenant by schema. `/api/v1/` only for new APIs. Layered Django+DRF. No invented fiscal rules. Research tickets (`[research]` / `/deerflow`) are docs-only.

Frequently asked questions