Loading...
Loading...
Found 31 Skills
Use this skill for Makefile audit and optimization. Use when auditing Makefiles, reviewing build system, checking portability, eliminating recipe duplication. Do not use when creating new Makefiles - use abstract:make-dogfood. DO NOT use when: architecture review - use architecture-review.
Run post-deployment smoke checks with Makefile targets (`remote-status`, `remote-logs`) plus optional health URL checks. Use after deployment to verify runtime state before final acceptance.
This skill should be used when users want to create, convert, or manage Justfiles for command automation. It handles converting Makefile, npm scripts, or shell commands to Justfile format, generating project-specific templates, and providing Justfile syntax guidance. Triggers on requests mentioning justfile, just command, command runner, Makefile conversion, or task automation.
Validate, lint, audit, or check Makefiles and .mk files for errors.
Analyze project and generate or enhance build automation file (Makefile, Taskfile.yml, Justfile, Magefile.go). If a build file already exists, improves it by adding missing targets and best practices. Use when user says "generate makefile", "create taskfile", "add justfile", "setup mage", or "build automation".
Used when you need to compile embedded firmware projects based on bare Makefiles (without CMake/IDE), call the built-in script to parse the Makefile, execute make, and locate firmware artifacts.
Comprehensive toolkit for generating best practice Makefiles following current standards and conventions. Use this skill when creating new Makefiles, implementing build automation, or building production-ready build systems.
Manage `chronic` wrapper for suppressing noisy command output in shell commands. Use this skill proactively whenever: (1) Running shell commands that produce verbose output on success (builds, linters, formatters, tests, migrations, deploys), (2) A command wrapped in chronic is hiding output you or the user actually need to see, (3) Reviewing or writing Justfiles, Makefiles, CI scripts, or shell scripts that invoke build/check/lint/test commands. Chronic runs a command silently on success but shows full output on failure.
Detects ESLint configuration and available commands in a repository. Returns structured JSON output designed for consumption by the quality-gates-linter agent. Checks for ESLint config files, extracts lint commands from package.json, Makefile, and CLAUDE.md, and provides command sources for the agent to read directly.
Lint Docker Compose files for Makefile-first deployment environments using .deploy.env.common + .deploy.env.<ENV_MODE>. Use when validating local/test/prod/custom compose files for image/build declaration, restart, healthcheck, logging, and external network settings.
MUST USE for anything related to mise, development tool versions, or dev environment setup. Triggers: (1) User mentions mise, mise.toml, .tool-versions, or mise commands like 'mise use', 'mise install', 'mise run'. (2) User wants to install, switch, pin, upgrade, or check versions of dev tools — node, python, go, ruby, java, rust, etc. — at project or global level, even without mentioning mise (e.g. 'set up node 22', 'what python version', 'upgrade go', 'check for outdated tools', 'configure dev environment'). (3) User wants to manage per-project environment variables via config files (e.g. 'add DATABASE_URL env var', 'set up env vars for different environments'). (4) User wants to define or run project tasks via mise (e.g. 'create a build task', 'run tests with mise'). Do NOT trigger for: Dockerfiles, package.json scripts, Makefiles, nvm/pyenv/rbenv commands, pip/npm package installation, git tags, CI/CD config, or deployment.
PostHog developer CLI and repo tooling reference. Use when the user mentions hogli, asks about repo CLI tools, bin scripts, Makefiles, how to run/build/test/lint, or any dev environment commands.