菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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 | volo-admin-console-generated-conflicts |
| description | 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. |
Use this skill when a volosoft/volo PR has conflicts caused by React Admin Console generated output under abp/admin-console/src/Volo.Abp.AdminConsole/wwwroot/admin-console, especially after release-to-dev auto-merge PRs.
gh for PR access because the repository may be private.abp/admin-console/AGENTS.md before changing files in that subtree.wwwroot/admin-console output may be ignored by .gitignore on newer branches and rebuilt by Volo.Abp.AdminConsole.csproj during pack.gh pr view <number> --json headRefName,baseRefName,mergeStateStatus,urlgh pr checkout <number>git fetch origin <baseRefName>git merge origin/<baseRefName>wwwroot/admin-console and added it to .gitignore, use git rm -r -f abp/admin-console/src/Volo.Abp.AdminConsole/wwwroot/admin-console and do not force-add rebuilt ignored files unless the user explicitly asks.react-app files such as route-config.ts, package.json, and package-lock.json.package.json.abp/admin-console:
powershell -ExecutionPolicy Bypass -File .\build-and-pack.ps1 -Configuration Releasegit add -Agit diff --name-only --diff-filter=U is empty.^(<<<<<<<|=======|>>>>>>>).git commit --no-editgit push origin <headRefName>gh pr view <number> --json mergeStateStatus,headRefOid,urlDIRTY means conflicts remain. BLOCKED usually means checks, reviews, or branch rules rather than conflicts.build-and-pack.ps1 runs npm install, npm run build, copies dist to wwwroot/admin-console, and runs dotnet pack.npm run build:wwwroot from MSBuild, so generated files can exist locally after the build while remaining ignored by Git.