oma-dev-workflow — Claude Code skill: setup and install
The oma-dev-workflow Claude Code skill configures development tasks, Git hooks, CI/CD, and release automation. It runs when a repository workflow needs to be created or fixed.
MIT ★ 1,472 updated 2026-10-29
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a claude-codeWhat oma-dev-workflow does
The skill sets up and runs repeatable development workflows, from mise tasks and code checks to migrations, i18n builds, and release preparation. It inspects the monorepo and its existing commands, preserves the project's tool choices, and connects checks to hooks or CI/CD.
It needs mise, project task definitions, runtime versions, and the package managers used by those tasks. Selected language toolchains and a locally provisioned commitlint are also dependencies; hooks do not download packages. A skipped check does not count as a pass, even if the process exits with code 0.
Tasks can start development servers, run tests or builds, generate clients, and execute migrations. They may write project files. Before running an unfamiliar task, the skill reads its definition; destructive tasks require confirmation.
What it helps with
- set up
misetasks for monorepo checks - connect
commitlintto thecommit-msghook - add app checks to CI/CD
- diagnose a failing
misetask - prepare an i18n build or release workflow
Example prompts for the agent
- Set up
misedevelopment tasks for the apps in this monorepo. - Connect
commitlintto thecommit-msghook and add checks to CI. - Find out why the
misetest task fails.
How to install oma-dev-workflow
1Skills CLI (Vercel)
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a claude-code2Manually: put the files in place
~/.claude/skills/oma-dev-workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/oma-dev-workflow/
1Skills CLI (Vercel)
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a codex2Manually: put the files in place
.agents/skills/oma-dev-workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a cursor2Manually: put the files in place
.cursor/skills/oma-dev-workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install first-fluke/oh-my-agent skills/oma-dev-workflow2Manually: put the files in place
.github/skills/oma-dev-workflow/SKILL.md1Skills CLI (Vercel)
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/first-fluke/oh-my-agent --path skills/oma-dev-workflowManually: put the files in place
.devin/skills/oma-dev-workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about oma-dev-workflow
How do I install oma-dev-workflow in Claude Code?
Run npx skills add first-fluke/oh-my-agent --skill oma-dev-workflow -a claude-code.
What does oma-dev-workflow do?
It configures and runs development tasks, checks, Git hooks, CI/CD, and release automation. The skill works with the project's existing tools and verifies task results.
What does oma-dev-workflow need to run?
It needs mise, project task definitions, runtime versions, and the package managers used by those tasks. Selected language toolchains and a locally installed commitlint are also required.
Source text
SKILL.md · MIT
---
name: oma-dev-workflow
description: Configure development tasks, git hooks, CI/CD, or release
automation. Use when creating or fixing a repository development workflow.
---
# Dev Workflow - Monorepo Task Automation Specialist
## Scheduling
### Goal
Set up, run, optimize, and troubleshoot reproducible development workflows using `mise`, language-specific checks, commitlint, validation pipelines, CI/CD, migrations, i18n builds, and release coordination.
### Intent signature
- User asks about dev servers, mise tasks, lint/format/typecheck/test/build, git hooks, CI/CD, migrations, generated clients, i18n builds, or release automation.
- User needs workflow execution or developer environment setup rather than product feature implementation.
- User asks to configure Ruff/pyrefly, Biome/TypeScript 7, Dart/Flutter checks, Hadolint, or commitlint.
### When to use
- Running development servers for monorepo with multiple applications
- Executing lint, format, typecheck across multiple apps in parallel
- Managing database migrations and schema changes
- Generating API clients or code from schemas
- Building internationalization (i18n) files
- Executing production builds and deployment preparation
- Running parallel tasks in monorepo context
- Setting up pre-commit validation workflows
- Configuring language-specific lint, format, and typecheck tools, Dockerfile linting, and commit-message validation
- Troubleshooting mise task failures or configuration issues
- Optimizing CI/CD pipelines with mise
### When NOT to use
- Database schema design or query tuning -> use DB Agent
- Backend API implementation -> use Backend Agent
- Frontend UI implementation -> use Frontend Agent
- Mobile development -> use Mobile Agent
### Expected inputs
- Requested workflow operation, affected apps/packages, and current monorepo structure
- Project manifests, lockfiles, tool configs, `mise.toml`, task definitions, CI files, hook manager, and failure logs when relevant
- Desired validation, setup, or release outcome
### Expected outputs
- Executed or documented mise task workflow
- Updated workflow config, CI/CD pipeline, hooks, env template, or release guidance when requested
- Project-local tool dependencies/configs and runnable `lint`, `format`, `format:check`, `typecheck`, and commitlint tasks for the selected profiles
- Status report with commands, outputs, failures, and next actions
### Dependencies
- `mise`, project task definitions, runtime versions, package managers behind mise tasks
- Resource guides for mise basics, tooling profiles, validation, example task wiring, release coordination, and troubleshooting (References)
- Selected language toolchains and locally provisioned commitlint; no package downloads from Git hooks
## Structural Flow
### Transitions
- If runtime versions changed, run `mise install`.
- If changed-file tasks exist, prefer changed-scope validation.
- If port is occupied, resolve or select another port before starting dev server.
- If a task is unfamiliar, read its definition before running.
- For setup, preserve existing tools and commands; apply language defaults only where configuration is missing. For execution-only requests, use existing checks without installing or replacing tools.
- `/stack-set` detects and records the stack. This skill owns tool setup and task/CI wiring; domain skills consume the resulting verification commands.
### Failure and recovery
- If task is missing, run `mise tasks --all`.
- If runtime is missing, run or recommend `mise install`.
- If task hangs, check for prompts or long-running dev-server behavior.
- If destructive task is requested, require confirmation.
- If a selected checker cannot run, report that check as incomplete and fix its setup within scope; do not replace it with a passing placeholder or a build.
- If a hook skips because another check is still running and exits 0, that push was not validated. Stop the owned previous run, or exit nonzero. Do not hide a gate failure with `|| true`.
### Exit
- Success: workflow runs or config changes are verified.
- Partial success: task failures, missing runtime, or CI/environment blockers are explicit.
## Logical Operations
### Canonical command path
1. Identify the affected apps/packages and the requested workflow outcome. Inspect affected app manifests, lockfiles, tool configs, `mise.toml`, CI, hooks, env patterns, and any `stack/stack.yaml`. Read task definitions and use `mise tasks --all` to discover existing commands. Determine whether tasks can run in parallel or must be sequential.
2. For setup or tool changes, load the selected tooling profiles from References. Configure missing dependencies, settings, and tasks with the detected package manager; preserve existing tool choices. For checks alone, skip setup.
3. Expose applicable checks as `lint`, `format:check`, and `typecheck`; keep mutating `format` separate. A `check` task can aggregate non-emitting checks. Connect existing stack `verify.syntax.cmd` to that task without adding unsupported schema keys; preserve `verify.tests` and domain-specific scans.
4. For hook/CI setup, load the validation pipeline. Provision locked local tools first, preserve the existing hook manager, and connect commitlint to the local `commit-msg` hook. Staged lint stays on pre-commit. Typecheck the whole affected app on the push gate when commit time is the constraint. Configure CI for app checks and tests; integration tests stay out of default hooks and required CI (Guardrails).
5. Before relaunching local validation, follow the validation pipeline's repeated-run guidance. A skipped run is not a pass. Run the configured `mise run check` aggregate, or the applicable individual `lint`, `format:check`, and `typecheck` tasks, plus the relevant hermetic tests. Do not start Docker or external services for validation. Run each underlying checker once. Use `mise run //{path}:{task}` for configured monorepos; typecheck the complete affected app rather than individual changed files. Check exit codes, logs, generated artifacts, and CI compatibility.
6. Report the selected tools, commands, checks passed, and any unavailable or inapplicable checks. Include command status, duration, failures, and next steps. Builds remain subject to the execution policy.
### Resource scope and effects
Reads and edits `mise.toml`, CI configs, hook configs, scripts, and env templates. Running tasks may start dev servers (which occupy ports), run tests or builds, generate clients, or run migrations; they write build outputs, generated clients, and logs, and consume CPU and time.
### Guardrails
1. Use `mise run` tasks instead of direct package manager commands. Discover them with `mise tasks --all`; never assume a task exists
2. Run `mise install` after pulling changes or toolchain updates that change runtime versions
3. Read a task's definition and dependencies before running an unfamiliar task or modifying `mise.toml`
4. Use parallel tasks (`mise run lint`, `mise run test`) for independent operations. Cap concurrency when a measurement shows more workers slow the same suite
5. Run lint and test on changed scope, and configure CI to skip unchanged apps. Keep a repository selector that already fails closed on shared or unknown paths; do not replace it with the generic affected-checks helper
6. Validate commit messages with commitlint before committing
7. Run the pre-commit validation pipeline for staged files only, and never commit past a failing staged lint. Typecheck the whole affected app on the push gate when doing it on every commit would dominate commit time
8. Check task output and exit codes, and investigate the root cause of a failure instead of ignoring it
9. Document task dependencies in mise.toml comments and use consistent task naming conventions across apps
10. Enable mise in CI/CD pipelines and pin runtime versions in mise.toml for reproducible runs
11. Try new or changed tasks locally before committing CI/CD changes that depend on them
12. Never fetch packages from a Git hook. When a mise task already runs a checker, call that task. A hook running under `mise exec` may call the pinned local binary directly
13. Never run dev servers without checking port availability first
14. Never hardcode secrets in mise.toml files
15. Never run destructive tasks (clean, reset) without confirmation
16. Always quote task names containing `:` in mise.toml (`[tasks."lint:changed"]`) — unquoted colons fail TOML parsing
17. Always set `monorepo_root = true` (plus `[monorepo].config_roots`) in the root mise.toml before using `//path:task` syntax
18. Keep check tasks non-mutating; run format/fix tasks only within the requested edit scope, and never rewrite unstaged changes from a Git hook
19. Prefer hermetic tests: do not introduce tests that need Docker, containers (including testcontainers), or external services. If unavoidable, isolate them in a separate opt-in integration task, document the dependency, and keep that task out of `git:pre-commit`, `git:pre-push`, `validate:changed`, and required CI gates
## References
| Resource | Load when |
|----------|-----------|
| [resources/mise-basics.md](resources/mise-basics.md) | Installing or verifying mise, monorepo layout and root config, task syntax and dependencies, env templates, report templates |
| [resources/tooling-profiles.md](resources/tooling-profiles.md) | Configuring or changing Python, JS/TS, Dart/Flutter, Dockerfile, or commitlint tooling |
| [resources/validation-pipeline.md](resources/validation-pipeline.md) | Git hooks, CI/CD, change-based testing, repeated local validation |
| [resources/example-task-wiring.md](resources/example-task-wiring.md) | Wiring migrations, optional local Docker infra (not a test dependency), API client generation, or i18n builds into tasks |
| [resources/release-coordination.md](resources/release-coordination.md) | Versioning, changelog, releases |
| [resources/troubleshooting.md](resources/troubleshooting.md) | A task is missing, hangs, or fails on runtime, port, or configuration problems |
| `references/_shared/core/clarification-protocol.md` | A missing fact changes the outcome |
| `references/_shared/core/difficulty-guide.md` | Unresolved scope or dependencies |
### Knowledge Reference
mise, task runner, monorepo, dev server, lint, format, test, typecheck, build, deployment, ci/cd, parallel execution, workflow, automation, tooling
© first-fluke · MIT · first-fluke/oh-my-agent