workflow-automation_skill

Overview

This skill automates repetitive development tasks and standardizes workflows for teams and projects. It bundles npm scripts, a Makefile interface, Git hooks (Husky + lint-staged), shell task runners, and a GitHub Actions CI workflow to provide reliable, idempotent automation. Use it to speed onboarding, enforce quality checks, and streamline builds and deployments.

How this skill works

The skill provides a collection of reusable automation artifacts: npm scripts for common commands, a Makefile as a platform-agnostic entry point, Husky hooks with lint-staged for pre-commit checks, shell scripts for environment setup and deployment, and a GitHub Actions workflow for CI. Scripts include safety checks, clear error messages, and idempotent operations so repeated runs are safe. CI runs linting, type checks, and tests, while task scripts handle environment bootstrapping and deploy orchestration.

When to use it

• You repeat the same local commands across projects or team members
• You need a multi-step build pipeline combining lint, type-check, tests, and bundling
• You want consistent pre-commit checks and enforced code quality
• You need reproducible developer environment setup (containers, migrations)
• You want a simple, testable CI pipeline on GitHub Actions

Best practices

• Expose core actions as npm scripts and call them from Makefile to support cross-platform use
• Keep scripts idempotent and fail with clear, actionable messages
• Do not hardcode secrets; use env files and CI secrets management
• Run lint and type checks in pre-commit hooks and CI to catch issues early
• Document scripts with comments and provide a help target in Makefile

Example use cases

• Add npm scripts for dev, build, test, lint, format, and docker commands for a Node.js project
• Provide a Makefile that maps high-level commands (dev, ci, deploy) to npm scripts for simplicity
• Install Husky and lint-staged to auto-fix staged files and run type checks before commit
• Create a dev-setup.sh to install deps, create .env from .env.example, start Docker services, wait for DB, run migrations, and seed optionally
• Implement deploy.sh to build, test, and perform environment-aware deployment steps via SSH