菜单
Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-dev-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | oma-dev-workflow |
| description | Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination. |
Set up, run, optimize, and troubleshoot reproducible development workflows in monorepos using mise, task automation, validation pipelines, CI/CD, migrations, i18n builds, and release coordination.
mise.tomlmise, project task definitions, runtime versions, package managers behind mise tasksmise.toml files and available tasks.mise install.mise tasks --all.mise install.| Action | SSL primitive | Evidence |
|---|---|---|
| Read task definitions | READ | mise.toml, CI config |
| Select task strategy | SELECT | Parallel/sequential/changed-scope |
| Run workflow commands | CALL_TOOL | mise run, mise install, mise tasks |
| Write workflow config | WRITE | Hooks, CI, env templates |
| Validate outputs | VALIDATE | Exit codes, logs, artifacts |
| Report status | NOTIFY | Final workflow summary |
mise, shell, CI/CD tooling, project package manager tasks behind misemise tasks --all
mise install
mise run lint
mise run test
For app-specific tasks:
mise run //{path}:{task}
| Scope | Resource target |
|---|---|
CODEBASE | mise.toml, CI configs, scripts, generated clients |
LOCAL_FS | Env templates, build outputs, logs |
PROCESS | mise, build, test, lint, dev-server commands |
CREDENTIALS | Secrets must not be hardcoded in workflow configs |
mise run tasks instead of direct package manager commandsmise install after pulling changes that might update runtime versionsmise run lint, mise run test) for independent operationslint:changed, test:changed)mise tasks --all to discover available tasks before runningmise install after toolchain version updatesmise tasks: in mise.toml ([tasks."lint:changed"]) — unquoted colons fail TOML parsingmonorepo_root = true (plus [monorepo].config_roots) in the root mise.toml before using //path:task syntax# Install mise
curl https://mise.run | sh
# Activate in shell
echo 'eval "$(~/.local/bin/mise activate)"' >> ~/.zshrc
# Install all runtimes defined in mise.toml
mise install
# Verify installation
mise list
project-root/
├── mise.toml # Root task definitions
├── apps/
│ ├── api/ # Backend application
│ │ └── mise.toml # App-specific tasks
│ ├── web/ # Frontend application
│ │ └── mise.toml
│ └── mobile/ # Mobile application
│ └── mise.toml
├── packages/
│ ├── shared/ # Shared libraries
│ └── config/ # Shared configuration
└── scripts/ # Utility scripts
The root mise.toml must enable monorepo task paths, or every //path:task invocation fails with "require a monorepo root configuration":
# Root mise.toml — monorepo_root is a top-level key (before any [table])
monorepo_root = true
[monorepo]
config_roots = ["apps/*", "packages/*"]
Root-level tasks:
mise run lint # Lint all apps (parallel)
mise run test # Test all apps (parallel)
mise run dev # Start all dev servers
mise run build # Production builds
App-specific tasks:
# Syntax: mise run //{path}:{task}
# Requires monorepo_root = true in root mise.toml (see Project Structure)
mise run //apps/api:dev
mise run //apps/api:test
mise run //apps/web:build
TOML quoting rule: task names containing : must be quoted — [tasks."gen:api"], never [tasks.gen:api] (unquoted colons are a TOML parse error).
| Task Type | Purpose | Example |
|---|---|---|
dev | Start development server | mise run //apps/api:dev |
build | Production build | mise run //apps/web:build |
test | Run test suite | mise run //apps/api:test |
lint | Run linter | mise run lint |
format | Format code | mise run format |
typecheck | Type checking | mise run typecheck |
migrate | Database migrations | mise run //apps/api:migrate |
| Topic | Resource File | When to Load |
|---|---|---|
| Validation Pipeline | resources/validation-pipeline.md | Git hooks, CI/CD, change-based testing |
| Database & Infrastructure | resources/database-patterns.md | Migrations, local Docker infra |
| API Generation | resources/api-workflows.md | Generating API clients |
| i18n Patterns | resources/i18n-patterns.md | Internationalization |
| Release Coordination | resources/release-coordination.md | Versioning, changelog, releases |
| Troubleshooting | resources/troubleshooting.md | Debugging issues |
Define dependencies in mise.toml:
[tasks.build]
depends = ["lint", "test"]
run = "echo 'Building after lint and test pass'"
[tasks.dev]
depends = ["//apps/api:dev", "//apps/web:dev"]
Parallel (independent tasks):
# Runs all lint tasks simultaneously (via depends)
mise run lint
# mise-native parallel execution of multiple tasks
mise run lint ::: test
Sequential (dependent tasks):
# Runs in order: lint → test → build
mise run lint && mise run test && mise run build
Mixed approach:
# Start dev servers in background
mise run //apps/api:dev &
mise run //apps/web:dev &
wait
Common patterns for monorepo env vars:
# Database
DATABASE_URL=postgresql://user:pass@localhost:5432/db
# Cache
REDIS_URL=redis://localhost:6379/0
# API
API_URL=http://localhost:8000
# Frontend
PUBLIC_API_URL=http://localhost:8000
When setting up development environment:
mise list)When running tasks:
When troubleshooting:
mise config, mise doctor)| Issue | Solution |
|---|---|
| Task not found | Run mise tasks --all to list available tasks |
| Runtime not found | Run mise install to install missing runtime |
| Task hangs | Check for interactive prompts, use --yes if available |
| Port already in use | Find process: lsof -ti:PORT then kill |
| Permission denied | Check file permissions, try with proper user |
| Missing dependencies | Run mise run install or app-specific install |
Follow the core workflow step by step:
Vendor-specific execution protocols are injected automatically by oma agent:spawn.
Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.
../_shared/core/clarification-protocol.md../_shared/core/difficulty-guide.mdmise, task runner, monorepo, dev server, lint, format, test, typecheck, build, deployment, ci/cd, parallel execution, workflow, automation, tooling