Script and automate repetitive tasks and workflows.
Release Wolf - Pre-deployment QA gatekeeper. Run before any production deploy. Checks for exposed secrets, broken links, Lighthouse performance scores, and visual regressions. Invoke with /prodcheck or when user mentions 'release check', 'deploy check', 'pre-launch', 'go/no-go', or 'production ready'.
GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" commands, "github cli", searching repos for files/directories (.skilz, .cursor, .codex, Dockerfile), monitoring GitHub Actions workflows, checking PR CI status, downloading artifacts, creating PRs/issues/repos from command line, triggering workflows, forking repos, batch operations, "write a workflow", "github actions", "CI/CD pipeline", "workflow yaml", and "matrix builds". Use for gh search, gh run, gh pr, gh issue, gh repo, gh workflow, gh api, workflow authoring, and automating GitHub operations.
Review code changes for bugs, quality, and project compliance. Works on PRs or local changes. Use when asked to review a PR, review changes, check code quality, or audit for bugs.
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
User-specific git workflow preferences and edge case handling. Documents commit message format requirements and pre-commit hook retry logic specific to this user. Use when creating commits or handling pre-commit hook failures.
Rules and procedures for Git operations (add, branch, commit, push). Use when performing git add, git commit, git push, or creating branches.
Multi-agent code review orchestration following 2024-2025 best practices. Use when: - Reviewing code changes before commit or merge - PR review with comprehensive analysis needed - Security audit of code changes - Architectural review of significant changes - AI-generated code needs validation - Team code quality enforcement Do NOT use for: - Simple typo fixes (direct review is faster) - Documentation-only changes - Single-line changes without logic
Create, checkout, rebase, and manage git branches following Carbon ACX naming conventions and workflows.
This skill should be used when user asks to commit changes to git repository. Triggers on Ukrainian/English phrases like "закоміть зміни", "commit changes", "створи коміт", "зроби коміт", or any request to create git commits. Creates atomic commits with semantic file grouping using conventional commit format.
Automates creation and management of headless git worktree structures. Use when the user requests to clone a repository with worktree setup, convert an existing repository to use worktrees, or add new worktrees to a bare repository. Triggers on requests like "set up worktrees", "headless git setup", "bare repo with worktrees", or "add a worktree for branch X".
Quality verification before commits and deployments. Use for quality checks, running tests, checking coverage, validating changes.
Build production-quality Terraform code following best practices. Use when creating Terraform code, modules, or .tf files. Also for reviewing/validating Terraform against standards.
Autonomous 21-phase project audit with testing, security scanning, code quality, GitHub auditing, and auto-fixing
Quality assurance and testing toolkit for OpenTofu/Terraform infrastructure as code. Use this skill when reviewing, testing, or validating OpenTofu/Terraform configurations. This skill runs automated QA checks (tofu fmt, tofu validate, tflint, trivy) and validates code against client-specific conventions and best practices. Ideal for code review, pre-commit validation, and ensuring IaC quality standards.
Enforces strict GitHub workflow hygiene and best practices. Use this skill for ALL git and GitHub operations including commits, branches, pull requests, and repository management. Core rules - NEVER commit directly to main/master, ALWAYS work on feature branches, use GitHub MCP for all GitHub API operations (issues, PRs, reviews), require PRs for all merges. Triggers on any git command, GitHub operation, or when starting new feature work.
Scan project for outdated or vulnerable dependencies, enforce dependency policies, check licenses, and generate upgrade recommendations.
Automatically deploys to Vercel production, uses Vercel MCP to fetch build logs, analyzes errors, fixes them, and retries until successful deployment. Use when deploying to production or fixing deployment issues.
Git best practices and workflows including conventional commits, branching strategies, and collaboration patterns.
Security review workflow for GitHub repositories using the Security MCP (OWASP ASVS + NIST 800-53) as the primary reference and mapping layer. Use when asked to security review a repo, produce an OWASP/NIST-aligned checklist, map findings to ASVS/NIST controls, generate a prioritized vulnerability report, or create security requirements/acceptance criteria from repo code/config.
Analyze staged changes and create meaningful git commits with appropriate commit messages following conventional commit standards. Automatically groups changes into logical units and presents multiple commit options (single vs. multiple commits) before execution. Always waits for user confirmation.
Use when working with git operations including commits, branches, worktrees, PRs, and Graphite stacked PRs. Covers the full git workflow from feature isolation to PR submission.
Expert guidance for creating and maintaining GitHub Actions workflows and reusable workflows with security best practices
