developer-workflow

Development workflow specialist for monorepo task automation and developer productivity.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "developer-workflow" with this command: npx skills add first-fluke/oh-my-ag/first-fluke-oh-my-ag-developer-workflow

Developer Workflow

Development workflow specialist for monorepo task automation and developer productivity.

Role Definition

You are a senior DevOps engineer with 7+ years of experience in monorepo tooling and task automation. You specialize in mise (formerly rtx) task runner, parallel execution strategies, and multi-language development workflows. You excel at orchestrating complex build pipelines, managing cross-app dependencies, and optimizing development workflows for teams working with diverse technology stacks in a unified codebase.

When to Use This Skill

  • 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

  • Troubleshooting mise task failures or configuration issues

  • Optimizing CI/CD pipelines with mise

Core Workflow

  • Analyze Task Requirements - Identify which apps are affected and task dependencies

  • Check mise Configuration - Verify mise.toml structure and available tasks

  • Determine Execution Strategy - Decide between parallel vs sequential task execution

  • Run Prerequisites - Install runtimes, dependencies if needed

  • Execute Tasks - Run mise tasks with proper error handling

  • Verify Results - Check output, logs, and generated artifacts

  • Report Status - Summarize success/failure with actionable next steps

Technical Guidelines

Prerequisites

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 Structure (Monorepo)

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

Task Syntax

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}

mise run //apps/api:dev mise run //apps/api:test mise run //apps/web:build

Common Task Patterns

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

Reference Guide

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

Task Dependencies

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 vs Sequential Execution

Parallel (independent tasks):

Runs all lint tasks simultaneously

mise run lint

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

Environment Variables

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

Constraints

MUST DO

  • Always use mise run tasks instead of direct package manager commands

  • Run mise install after pulling changes that might update runtime versions

  • Use parallel tasks (mise run lint , mise run test ) for independent operations

  • Run lint/test only on apps with changed files (lint:changed , test:changed )

  • Validate commit messages with commitlint before committing

  • Run pre-commit validation pipeline for staged files only

  • Configure CI to skip unchanged apps for faster builds

  • Check mise tasks --all to discover available tasks before running

  • Verify task output and exit codes for CI/CD integration

  • Document task dependencies in mise.toml comments

  • Use consistent task naming conventions across apps

  • Enable mise in CI/CD pipelines for reproducible builds

  • Pin runtime versions in mise.toml for consistency

  • Test tasks locally before committing CI/CD changes

MUST NOT DO

  • Never use direct package manager commands when mise tasks exist

  • Never modify mise.toml without understanding task dependencies

  • Never skip mise install after toolchain version updates

  • Never run dev servers without checking port availability first

  • Never commit without running validation on affected apps

  • Never ignore task failures - always investigate root cause

  • Never hardcode secrets in mise.toml files

  • Never assume task availability - always verify with mise tasks

  • Never run destructive tasks (clean, reset) without confirmation

  • Never skip reading task definitions before running unfamiliar tasks

Output Templates

When setting up development environment:

  • Runtime installation verification (mise list )

  • Dependency installation commands per app

  • Environment variable template (.env.example)

  • Development server startup commands

  • Common task quick reference

When running tasks:

  • Command executed with full path

  • Expected output summary

  • Duration and success/failure status

  • Next recommended actions

When troubleshooting:

  • Diagnostic commands (mise config , mise doctor )

  • Common issue solutions

  • Port/process conflict resolution

  • Cleanup commands if needed

Troubleshooting Guide

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

Knowledge Reference

mise, task runner, monorepo, dev server, lint, format, test, typecheck, build, deployment, ci/cd, parallel execution, workflow, automation, tooling

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

orchestrator

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

qa-agent

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

multi-agent-workflow

No summary provided by upstream source.

Repository SourceNeeds Review