kienbui1995/magic-powers/ado-pipeline-optimization
Claude Code and agent skill by kienbui1995/magic-powers
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when improving Azure Pipelines performance — caching dependencies, parallel job strategies, artifact management between stages, test result publishing, code coverage gates, and reducing pipeline runtime.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-pipeline-optimizationSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-pipeline-optimization.
ADO Pipeline Optimization
When to Use
- Pipeline taking more than 15 minutes and needs to be faster
- Wasting parallel job minutes on redundant work
- Test results not visible in Azure DevOps Tests tab
- Code coverage not being tracked or trending over time
- Artifact sharing between stages causing issues
- Flaky or redundant jobs increasing cost without adding value
Core Jobs
1. Dependency Caching
Cache hits reduce dependency install time from 2-5 minutes down to seconds. The key must include the lockfile to invalidate when dependencies change.
2. Parallel Jobs Strategy
3. Test Splitting for Parallel Execution
4. Publishing Test Results & Coverage
5. Build Once, Deploy Many
6. Pipeline Timing Analysis
Key Concepts
- Cache task — stores and restores directories between pipeline runs; cache key must include lockfile hash to invalidate properly
- Parallel jobs — independent jobs in the same stage run simultaneously on separate agents; each consumes one parallel job slot
- Pipeline artifact — build outputs stored in Azure DevOps storage; fast download in subsequent stages without re-downloading from external sources
- Test splitting — distribute test files across multiple agents;
System.JobPositionInPhaseandSystem.TotalJobsInPhaseidentify each shard - Publish test results — sends test XML to Azure DevOps for display in Tests tab; must use
condition: always()so failures are visible - restoreKeys — fallback cache keys tried in order when the exact key misses; enables partial cache hits
Checklist
- [ ] Dependencies cached (npm/pip/nuget) — cache key includes lockfile, not just package name?
- [ ] Independent jobs running in parallel (lint, typecheck, unit tests, docker build)?
- [ ] Build artifact published once and downloaded in deploy stages (not rebuilding)?
- [ ] Test results published with
condition: always()(visible in Tests tab even on failure)? - [ ] Code coverage published and trending visible in Coverage tab?
- [ ] Large test suites split across parallel agents using
strategy.parallel? - [ ] Pipeline timeline reviewed to identify the critical path (slowest chain of stages)?
Key Outputs
- Pipeline runtime reduced (target: less than 10 minutes for build and unit test stage)
- Test results visible in Azure DevOps Tests tab with pass/fail history
- Code coverage trending visible in Coverage tab over time
- Single build artifact reused across all deployment environments (identical binary)
Output Format
- 🔴 Critical — rebuilding application in every deploy stage (slow builds, inconsistent binary), test results not published (failures invisible in UI),
npm installinstead ofnpm ci(non-deterministic) - 🟡 Warning — no caching configured (reinstalling all dependencies on every run), all validation jobs sequential when they can run in parallel, cache key not including lockfile (cache never invalidates)
- 🟢 Suggestion — split large test suites across 4+ parallel agents, add code coverage threshold gate (fail if drops below 80%), review pipeline timeline to find the critical path bottleneck
Anti-Patterns
npm installinstead ofnpm ci(ignores lockfile, produces non-deterministic installs)- Missing
condition: always()on PublishTestResults (coverage data missing when tests fail — least useful time) - Downloading full source code in deploy stage and recompiling (defeats the purpose of build artifacts)
- Cache key not including lockfile — cache never invalidates when
package.jsonchanges - Publishing artifacts to both drop location AND pipeline artifact (redundant, slows pipeline)
- Setting
maxParalleltoo high — can exceed available parallel job slots and cause queuing
Integration
ado-pipeline-design— the pipeline structure to optimize; parallelism requires well-separated stagesado-pipeline-security— do not cache credential files or secrets alongside dependencies
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-pipeline-optimization/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-pipeline-optimization)