my-agents

Use ONLY when the user asks about ABP/VOLO/Lepton release QA generation, QA test cases from release branch diffs, or the old abp-release-qa-orchestrator workflow. Do not run the workflow directly; suggest the /generate-release-qa-test-cases command.

Revise article, documentation, blog post, and guide section headings so they use direct, concrete topic labels instead of rhetorical or AI-styled titles such as "Why X Matters", "What X Means", "How X Helps", or vague benefit-led headings. Use when editing headings, outlines, article titles, section titles, or table-of-contents labels for ABP community articles, technical blogs, documentation, release posts, tutorials, and similar written content.

Use when fixing volo PR merge conflicts in abp/admin-console generated React Admin Console assets, wwwroot/admin-console files, package-lock.json, route-config.ts, or build-and-pack.ps1 output.

Implement REST APIs in ABP Framework with AppServices, DTOs, pagination, filtering, and authorization. Use when building API endpoints for ABP applications.

Generate ABP Application.Contracts layer scaffolding (interfaces, DTOs, permissions) from technical design. Enables parallel development by abp-developer and qa-engineer. Use when: (1) backend-architect needs to generate contracts, (2) preparing for parallel implementation workflow, (3) creating API contracts before implementation.

Add translations to ABP Framework localization files using base language as reference. Use when: (1) adding new translation keys, (2) localizing new features, (3) updating existing translations across multiple languages.

Manage AbpDevTools virtual environments and environment apps with abpdev. Use when the user wants to configure connection-string environments, start/stop Docker-backed infra tools, or open a shell with a selected environment.

Use AbpDevTools maintenance and utility commands such as clean, replace, tools/config, notifications, update, find-file, find-port, and ABP Studio switching. Use when the user wants repo cleanup, config-driven text replacement, process/port inspection, tool updates, or local tool-path setup.

Handle an ABP GitHub issue end-to-end: analyze the issue, verify behavior from real ABP source and docs, validate with ABP lab projects when needed, and comment or create a PR from the correct milestone branch.

Handle an ABP support ticket end-to-end: read the support question, inspect screenshots, verify behavior from ABP source and docs, and produce a support-team answer in markdown.

Reference map for local ABP Framework, ABP Studio, and commercial module source trees. Use when working on ABP internals so the agent checks real implementations under C:\P\abp, C:\P\abp-studio, C:\P\volo, and C:\P\lepton instead of guessing.

Handle a GitHub issue end-to-end: analyze it, decide whether it needs an answer, a bug fix, or a feature implementation, then reply on the issue or create a PR that closes it. Always plan feature work first; bug fixes may be implemented directly.

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

Compile SCSS to CSS using Sass CLI with repo-aware defaults (direct file compile, watch mode, and compilerconfig.json mapping support). Use when: (1) user asks to compile .scss, (2) CSS output is missing/stale, (3) agent needs repeatable Sass commands.