Loading...
Loading...
Found 1,201 Skills
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
Find the pull request for the current branch on GitHub, GitLab, Bitbucket Cloud or Data Center, or Azure DevOps; retrieve unresolved inline CodeAnt AI review threads through the source-control provider; validate each finding; apply safe minimal fixes; verify them; and resolve only fixed threads. Use when asked to address, fix, triage, or resolve CodeAnt PR comments without installing or using codeant-cli.
Create, edit, migrate, check, and inspect just/justfile runners. Use when changing justfiles, migrating Makefile/npm scripts to just, linting house-style justfiles, or discovering via just --list/--show/--dump. NOT for shell scripts (shell-scripter), shell conventions (shell-conventions), CI YAML (devops-engineer), Make mtime builds, Compose, or mise.
Routes .NET/C# requests to the correct domain skill and loads coding standards as baseline for all code paths. Determines whether the task needs API, UI, testing, devops, tooling, or debugging guidance based on prompt analysis and project signals, then invokes skills in the right order. Always invoked after [skill:using-dotnet] detects .NET intent. Do not use for deep API, UI, testing, devops, tooling, or debugging implementation guidance.
Design schemas, plan migrations, and optimize queries. Six modes from modeling to evolution. Use for database architecture. NOT for DBA ops, backups, or deployment (devops-engineer).
Two-way traceability between commits and tickets. (A) When committing any change, make sure the commit message carries the ticket / work-item number — derive it from the user's words, the branch name, or the current task, ask if unknown (a commit-msg hook is bundled but install it only on explicit request). (B) When the user asks WHY code is the way it is — "why was this changed", "who decided this", "is this hardcode intentional", "ทำไมถึงแก้อันนี้", "มีเหตุผลป่าว" — trace the line through git blame/log to the commit, extract the ticket number from the message, fetch the ticket from the tracker (Azure DevOps, GitHub Issues, JIRA), INCLUDING downloading and reading attached images (requirements often live only in an annotated screenshot), and answer with commit + ticket evidence. Trigger on any commit request in a ticketed repo, on "install commit hook", and on any why-is-this-code-like-this / change-archaeology question — even when the user doesn't mention tickets.
Set up and run Git-backed schema sync between a repository and Prepr CMS environments, with schema files in prepr/schema/. Use this skill whenever the user wants to sync a Prepr schema via GitHub, GitLab, Bitbucket or Azure DevOps, get local schema file changes into a Prepr environment, export an environment's schema to the repository, promote schema between development, acceptance and production, add schema validation to CI, debug a schema import that fails or returns github.validation.failed, check whether the schema files and an environment have drifted, or asks why schema file edits have not appeared in Prepr. Also use it when the user considers direct environment-to-environment sync.
Integrate automated testing into CI/CD pipelines for continuous quality feedback. Use for continuous testing, CI testing, automated testing pipelines, test orchestration, and DevOps quality practices.
Docusaurus build health validation and deployment safety for Claude Skills showcase. Pre-commit MDX validation (Liquid syntax, angle brackets, prop mismatches), pre-build link checking, post-build health reports. Activate on 'build errors', 'commit hooks', 'deployment safety', 'site health', 'MDX validation'. NOT for general DevOps (use deployment-engineer), Kubernetes/cloud infrastructure (use kubernetes-architect), runtime monitoring (use observability-engineer), or non-Docusaurus projects.
Expert in Machine Learning Operations bridging data science and DevOps. Use when building ML pipelines, model versioning, feature stores, or production ML serving. Triggers include "MLOps", "ML pipeline", "model deployment", "feature store", "model versioning", "ML monitoring", "Kubeflow", "MLflow".
GitHub Actions, GitLab CI/CD, Jenkins, Azure DevOps, build and test strategies, and deployment patterns
Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Azure Load Testing with VNets/private endpoints, JMeter/Locust/Playwright, CI/CD pipelines, or Playwright Workspaces, and other Azure App Testing related development tasks. Not for Azure Test Plans (use azure-test-plans), Playwright Workspaces (use azure-playwright-workspaces), Azure DevOps (use azure-devops), Azure App Service (use azure-app-service).