メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | abp-release-qa-orchestrator |
| description | 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. |
This workflow is command-only.
Do not collect branches, generate markdown, run scripts, or create GitHub issues from this skill.
If the user wants ABP/VOLO/Lepton release QA test cases, suggest this command:
/generate-release-qa-test-cases framework_from=10.4 framework_to=10.5
Optional examples:
/generate-release-qa-test-cases framework_from=10.4 framework_to=10.5 lepton_from=5.4 lepton_to=5.5
/generate-release-qa-test-cases {"framework_from":"10.4","framework_to":"10.5","assignee":"gizemmutukurt"}
The command owns the scripts, validation rules, issue creation, and side effects.
