Use when diagnosing failed builds to quickly isolate fault class and restore delivery flow. USE FOR: identify first failing stage, map log signatures to likely causes, recommend smallest safe fix path, and produce validation checklist for CI and local runs. DO NOT USE FOR: writing new feature code, replacing incident…
Use when defining or operating a build-master control plane that keeps merges flowing while containing CI breakage. USE FOR: lane-state policy, break-fix eligibility, retry/revert thresholds, and escalation rules. DO NOT USE FOR: direct code implementation, bypassing branch protection, or approving high-risk fixes…
Use when designing or reviewing monorepo workflow isolation so independent layers (mobile, database, portal, extension, infra) can build, test, and release separately. USE FOR: define path-based lane boundaries, isolate deploy workflows by layer, design independent versioning lanes, audit cross-trigger coupling in…
Audits live GitHub repository governance controls and produces a markdown evidence pack. USE FOR: exporting branch protection and required checks, verifying merge queue and environment protections, auditing runners and security gates, and reporting policy-vs-live gaps. DO NOT USE FOR: writing application code…
Use when producing a raw CI/CD diagnostics snapshot with measured repository metrics only. USE FOR: collect PR lifecycle timing, queue/requeue stats, conflict counts, sprint merge-distribution buckets, and backlog deltas with source commands. DO NOT USE FOR: remediation plans, policy recommendations, workflow…
Use when isolating flaky CI tests with evidence-based quarantine windows and expiry policy. USE FOR: confirm flakiness, quarantine only after repeat evidence, and produce owner/expiry tracking. DO NOT USE FOR: hiding failures, permanently disabling tests, or replacing root-cause remediation.
Use when reviewing code, pull requests, or diffs for bugs and regressions. USE FOR: review pull request for bugs, inspect diff for regression risk, identify missing test coverage, rank review findings by severity, review refactor for edge cases. DO NOT USE FOR: writing new features, restyling code for preference…
Assess Docker build readiness with composable scripts that analyze Dockerfile structure, inspect dependency footprint, estimate image size, and report security posture in structured JSON suitable for automation and remediation planning. USE FOR: reviewing Dockerfile structure before containerization, estimating…
Scaffold containerization of a legacy app for Azure Container Apps or Kubernetes with Dockerfile, health probes, and deployment assets. USE FOR: containerize this legacy app, create a Dockerfile for production, migrate app to Azure Container Apps, add Kubernetes manifests and health checks, set up ACR build and push…
Use when implementing consumer-driven contracts, Pact verification, provider states, or integration test orchestration across services. USE FOR: add Pact contract tests between services, verify provider won't break consumers, set up Pact Broker in CI, orchestrate multi-service integration tests with Docker Compose…
Use when estimating Copilot CLI session cost, analyzing model routing efficiency, or mapping available usage APIs. USE FOR: estimate Copilot session cost, analyze expensive agent dispatches, recommend cheaper model routing, audit Copilot workflow token usage, document GitHub Copilot usage APIs. DO NOT USE FOR: general…
CQRS and Event Sourcing patterns for scalable, auditable distributed systems with command models, event stores, and read projections. USE FOR: design CQRS architecture for a service, implement event sourcing for audit history, separate command and query models, plan read model projections and replay, add saga…
Use when creating a new instruction file for a domain, language, or workflow in a customization repo. USE FOR: create a new instructions file, choose applyTo glob for an instruction, write guardrails for a coding workflow, add repository standards for a language, draft instruction frontmatter and naming. DO NOT USE…
Use when creating a new reusable skill with clear triggers, workflow steps, and starter assets in a customization repository. USE FOR: add a new SKILL.md file, design skill trigger phrases, decide if work belongs in a skill, scaffold skill folder with templates, write discovery-focused skill frontmatter. DO NOT USE…
Language-agnostic modernization guidance for incrementally replacing legacy applications using strangler fig, ACLs, and risk scoring. USE FOR: plan legacy app modernization strategy, choose rewrite versus refactor versus replace, design strangler fig migration, sequence service extraction by dependency risk, decide…
Use when reviewing schemas, migrations, indexes, query plans, or data contract safety. USE FOR: audit schema drift, migration rollback safety, index health, query risk, repository patterns. DO NOT USE FOR: UI copywriting, infrastructure-only tasks, generic code review.
Use when designing schemas, writing migrations, reviewing queries, or defining repository and indexing patterns for an application's data layer. USE FOR: design a relational schema, write migration with rollback support, review SQL for N+1 or missing indexes, build a data dictionary, define repository or data access…
Zero-downtime database migration patterns, blue-green cutovers, and rollback strategy guidance for production data changes. USE FOR: plan expand-contract schema migration, design blue-green database cutover, write Flyway versioned migration and undo scripts, prepare rollback plan for production schema change, validate…
Use when capturing ceremony outcomes into durable decision records. USE FOR: document decision, rationale, options considered, owner, and follow-up actions from standup, sprint, and release ceremonies. DO NOT USE FOR: writing implementation code, replacing full ADR workflows, or generating marketing content.
Use when an approved feature or fix should progress to production through governed automation with minimal human intervention. USE FOR: approve-once delivery orchestration, deterministic dry-run rehearsal of status/merge/escalation logic, and policy-aligned remediation payload generation for blocked stages. DO NOT USE…
Use when monitoring workcell BOM dependencies and cell health so blocker issues are opened when a cell fails and resolved when it recovers. USE FOR: dependency maps, cell health checks, blocker issue creation, and recovery closures. DO NOT USE FOR: general project tracking or unrelated CI triage.
VS Code Dev Containers and GitHub Codespaces guidance for reproducible development environments and team onboarding. USE FOR: create devcontainer.json for this repo, set up Codespaces for contributors, containerize local dev toolchain, add VS Code extensions inside container, make development setup reproducible across…
★not rated 4 todayA81 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: