From makefile-workflow
Design or update Makefiles with consistent build, format, lint, test, and check-* targets. Use when a user asks for a Makefile, build automation, or project workflow targets for Go, Node, Bazel, or mixed stacks.
npx claudepluginhub jaeyeom/claude-toolbox --plugin makefile-workflowThis skill uses the workspace's default tool permissions.
Create or refine Makefiles that encode a reliable developer workflow. Mirror the project's existing tooling (Go, Node, Bazel, Supabase, etc.) and use low-noise output for successful runs.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Create or refine Makefiles that encode a reliable developer workflow. Mirror the project's existing tooling (Go, Node, Bazel, Supabase, etc.) and use low-noise output for successful runs.
all, check, and fix targetsall: full local workflow (format + fix + tests + build + check-* targets)check: CI-friendly checks (no mutation), prefer check-* targetsformat + check-formatlint + fixtest, build, coverage, cleancheck-* over names like type-check, bundle-checkcheck-astro, check-bundlescripts/quiet-run.sh, wrap commands like:
@./scripts/quiet-run.sh "Label" <command>.PHONY for non-file targets and group related sections with comments.rg for file lists.node_modules or vendor directories.golangci-lint verification hashes if .golangci.yml is present.npm run <task> or pnpm run <task> to preserve project scripts.check-generated or check-format that fails on a dirty git diff.make -j (parallel execution):
format, fix) must declare dependencies to prevent concurrent writes. For example, fix should depend on format since both write to the same files.validate-full should depend on fix.check-format, lint, test) are safe to run in parallel and need no extra ordering..NOTPARALLEL to the Makefile.all: format fix test buildcheck: check-format lint test buildfix: format (both mutate files)lint-golangci, fix-golangci, verify-golangci-configcoverage, coverage-html, coverage-report, clean-coveragecheck-astro, check-bundle, test-e2e, db-push, db-reset, db-status, db-gen-typesWhen asked to create or update a Makefile: