smss123

Expert Azure DevOps + Git skill for managing repositories, branches, pull requests, pipelines, work items, and long-running tasks via sub-agents. Use this skill whenever the user mentions: Azure DevOps, ADO, Azure Repos, Azure Pipelines, YAML pipelines, git in ADO context, PRs in DevOps, branch policies, work items, sprints, backlogs, boards, service connections, release pipelines, build agents, PAT tokens, secrets, variable groups, Key Vault, CODEOWNERS, coverage gates, changelogs, semver, policy drift, rollbacks, conflict resolution, or multi-repo changes. Also trigger when the user wants to: clone/push/pull from ADO repos, manage branches at scale, run parallel tasks, coordinate sub-agents for long jobs, automate CI/CD, manage ADO via REST API, implement git flow, use git worktrees, handle merge conflicts, revert bad releases, monitor agent health, order feature dependencies, auto-assign PR reviewers, generate release notes, send Teams or email alerts, detect policy drift, automate versioning, audit agent

Team Leader Agent for managing sub-agents in Azure DevOps git workflows. Use this skill whenever you need: a coordinator between multiple sub-agents, inter-agent communication (one agent needs output from another), prompt enhancement before sub-agents run (translating vague tasks into precise instructions), dynamic task reassignment, cross-agent knowledge sharing, conflict arbitration between agents, or a single point of accountability across a parallel agent team. Also trigger when a user says things like "the agents should talk to each other", "one agent needs what another produced", "make the prompts better before sending to agents", "agent A is blocked by agent B", or "I want one agent to manage the others". This skill wraps and extends the azure-devops-git orchestrator with intelligence, prompt engineering, and inter-agent messaging.

Expert guide for developing applications with the ABP Framework (abp.io) using ASP.NET Core, DDD patterns, and Razor Pages / MVC UI. Use this skill whenever the user mentions ABP, abp.io, Volo.Abp, AbpModule, application services, aggregate roots, domain services, ABP CLI, IRepository, PermissionDefinitionProvider, IDataSeedContributor, Auto API Controllers, AbpDbContext, or any ABP-specific concept. Also trigger for questions about layered ABP project structure, startup templates, or ABP module dependencies. Always consult this skill before generating any ABP-related code, architecture advice, or explaining ABP concepts — even for seemingly simple questions like "how do I create an entity in ABP". source: "https://docs.abp.io/en/abp/latest/"

Best practices for high-performance Entity Framework Core (EF Core 8/9): fast read queries AND fast writes/inserts, plus high-throughput, data-intensive apps (concurrency, parallel/background jobs, streaming large datasets, resiliency, optimistic concurrency, bulk insert). ALWAYS-ON for EF Core projects: if the codebase references any EF Core package (Microsoft.EntityFrameworkCore*, Npgsql.EntityFrameworkCore.PostgreSQL, Pomelo.EntityFrameworkCore.MySql, Oracle/MySql EF providers) or contains a DbContext, DbSet properties, OnModelCreating, or a Migrations folder, consult and apply this skill before writing, generating, reviewing, refactoring, or fixing ANY data-access code in that project — even when performance, N+1, slow SaveChanges, or bulk insert are not explicitly mentioned. All fixes must preserve original behavior (same output). Also use for "review my EF Core query", "why is this insert slow", and "scale my EF Core app".