- Home
- Skills
- First Fluke
- Fullstack Starter
- Developer Workflow
developer-workflow_skill
- TypeScript
181
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill first-fluke/fullstack-starter --skill developer-workflow- SKILL.md7.8 KB
Overview
This skill is a developer workflow specialist for monorepo task automation using mise. I provide concrete steps to set up development environments, run and orchestrate mise tasks, optimize CI/CD, and troubleshoot common failures. The guidance focuses on reproducible builds, parallel execution, and safe task management across multiple apps.
How this skill works
I inspect mise configuration and the monorepo layout to determine which apps and tasks are affected. I choose an execution strategy (parallel vs sequential), ensure runtimes are installed with mise install, run mise run tasks with proper error handling, and validate outputs and exit codes. Finally I report concise next steps and remediation when tasks fail.
When to use it
- Starting or coordinating development servers across multiple apps in a monorepo
- Running lint/format/typecheck/test across apps, optimized for changed files
- Managing database migrations and local infra before running the backend
- Preparing production builds and release automation across services
- Optimizing CI/CD to skip unchanged apps and speed up pipelines
Best practices
- Always use mise run tasks instead of direct package manager commands when tasks exist
- Run mise install after pulling changes that might update runtime versions
- Use parallel mise run lint and mise run test for independent operations, and sequential runs for dependent steps
- Limit lint/test to changed apps (lint:changed, test:changed) to reduce feedback time
- Verify available tasks with mise tasks --all and pin runtimes in mise.toml for reproducibility
- Validate task output and exit codes in CI, and test tasks locally before changing CI/CD
Example use cases
- Bring up local dev servers: mise run //apps/api:dev & mise run //apps/web:dev & wait
- Run validation pipeline in CI that skips unchanged apps and reports failures
- Execute database migrations: mise run //apps/api:migrate and verify schema
- Run monorepo-wide lint and test in parallel: mise run lint && mise run test
- Prepare a release by running build, generating API clients, and producing changelogs
FAQ
Run mise tasks --all to list tasks and confirm the correct path and task name before modifying configuration.
When should I run mise install?
Run mise install after pulling changes that update runtime versions or whenever a task reports a missing runtime.