cross-project-pipeline-audit

name	cross-project-pipeline-audit
description	This skill should be used when the user asks to run a "cross-project pipeline audit", "multi-repo pipeline audit", or "audit all my pipelines" across 3+ repositories in parallel, or passes the `--team` flag on other skills. Dispatches the cicd-team-lead agent (running on the session model), which maps each repo's pipeline surface, partitions work into focused scopes (build validation, security posture, deployment path, runner fleet, observability, cross-repo patterns), dispatches parallel cicd-expert sub-agents (bounded by the fan-out budget), and consolidates findings into a unified report with overall verdict + per-repo deltas + cross-cutting pattern detection. Do NOT trigger on generic "audit my pipeline" (single-repo -- use `review-pipeline` or `audit-pipeline-security`).
argument-hint	[optional: --repos=<repo1,repo2,...> or repo paths]
allowed-tools	Agent, Read, Grep, Glob, Bash, TodoWrite, WebSearch, WebFetch, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs

Cross-Project Pipeline Audit

Dispatches the cicd-team-lead agent for multi-repo pipeline orchestration.

Step 1: Resolve repos

Parse user input for repo paths:

• --repos=api,web,mobile -- resolve to absolute paths
• Explicit paths provided by user
• If no repos specified, scan parent directory for repos with CI config

Confirm repo list and CI platform for each before dispatching.

Step 2: Dispatch cicd-team-lead

Read and inline its body (everything below the frontmatter) as the prompt prefix. Do NOT dispatch via -- plugin-namespaced dispatch silently strips the tool the team lead needs for sub-dispatch (see the agent file's RUNTIME DISPATCH NOTE -- a known Claude Code platform limitation).