Loading...
Loading...
Found 816 Skills
Azure DevOps Sprint 254-262 new features and enhancements (2025)
Expert bash/shell scripting system across ALL platforms. PROACTIVELY activate for: (1) ANY bash/shell script task, (2) System automation, (3) DevOps/CI/CD scripts, (4) Build/deployment automation, (5) Script review/debugging, (6) Converting commands to scripts. Provides: Google Shell Style Guide compliance, ShellCheck validation, cross-platform compatibility (Linux/macOS/Windows/containers), POSIX compliance, security hardening, error handling, performance optimization, testing with BATS, and production-ready patterns. Ensures professional-grade, secure, portable scripts every time.
CI/CD best practices for building automated pipelines, deployment strategies, testing, and DevOps workflows across platforms
Complete Azure DevOps automation - boards, repos, pipelines, artifacts
Professional DevOps engineering skill for creating CI/CD pipelines, implementing infrastructure as code, managing environments, and establishing monitoring and observability across all deployment stages.
Comprehensive Azure administration capabilities covering identity management, resource orchestration, CLI tooling, and DevOps automation. Auto-activates for Azure, az cli, azd, Entra ID, RBAC, and infrastructure tasks.
Install and configure Azure CLI with the Azure DevOps extension on macOS using Homebrew. Handles login, default organization/project configuration, and sanity checks. Use when the user wants to set up Azure DevOps CLI tools, install az cli, configure az devops defaults, or troubleshoot their Azure DevOps CLI setup on macOS.
Use the devopsellence CLI to choose solo or shared workspace mode, deploy the current app, inspect status, and manage secrets or nodes.
Configures an available test provider (e.g. Apex Unit Tests, Code Analyzer, Flow Tests, Provar) on a DevOps Center pipeline via the Connect API, after explicit user confirmation, so the provider's test suites become available for assignment to pipeline stages. Takes a pipelineId and a testProviderId. Use this skill when a provider is available on the pipeline but not yet configured and the user wants to enable it. TRIGGER when: the user wants to configure, enable, set up, or add a test provider on a pipeline, or wants a not-yet-configured provider's suites to become available. DO NOT TRIGGER when: re-syncing an already-configured provider to pick up new suites (use syncing-test-providers), or assigning existing suites to a stage (use managing-suite-assignments).
Create Azure DevOps work items from a backlog_input.json (the output of classify-work-items) via the bundled create-backlog.cs script. Always does a dry-run validation first and only creates real items after the user explicitly approves. Use this whenever there is a backlog_input.json or any file of items to file in ADO, or when the user says "create these work items", "file the backlog", "push these to Azure DevOps", "create the tickets/bugs/stories", "make the work items", or asks to turn a classified list of findings into a real ADO backlog. This is the step that actually writes to the org, so prefer it over hand-rolling REST/MCP calls when a backlog_input.json exists. After creating, it writes backlog_result.json for ado-writeback-tracking.
Show the Azure DevOps work items assigned to you as a clean, grouped table — open work first, sorted by state then priority, with the ticket number as a clickable link. Use whenever the user asks "what's on my plate", "my work items / my tasks", "what should I work on next", "show my backlog", "read my task hub", "daily standup prep", or starts the day wanting their remaining work. This is step 2 of the daily-work flow (read the task hub). Read-only — it lists, it never changes anything.
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge