菜单
Run mandatory pre-PR quality checks for .NET projects before creating a pull request. Use before creating any PR, or when the user says "prepare for PR", "pre-PR checks", or "quality gate".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/asynkron/asynkron-skills --skill pre-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | pre-pr |
| description | Run mandatory pre-PR quality checks for .NET projects before creating a pull request. Use before creating any PR, or when the user says "prepare for PR", "pre-PR checks", or "quality gate". |
| disable-model-invocation | true |
| argument-hint | [solution or project path] |
Check that required tools are available:
which roslynator
which quickdup
If roslynator is not found:
dotnet tool install -g roslynator.dotnet.cli
If quickdup is not found:
curl -sSL https://raw.githubusercontent.com/asynkron/Asynkron.QuickDup/main/install.sh | bashgo install github.com/asynkron/Asynkron.QuickDup/cmd/quickdup@latestThis is a mandatory quality gate to run before creating any pull request in a .NET project. It ensures code is analyzed, compiles cleanly, tests pass, duplication is checked, and code is formatted — in that order.
Do NOT skip any steps. Do NOT create a PR if any step fails. Iterate until all checks pass.
If $ARGUMENTS is provided, use it as the project/solution path. Otherwise, look for a .sln or .csproj in the current directory.
Also determine the source directory for quickdup scanning (typically src/ or the project root).
Run static analysis and auto-fix code issues:
roslynator fix $PROJECT_PATH
Then verify compilation:
dotnet build $PROJECT_PATH
If build fails: Fix the issues and rerun roslynator before proceeding.
dotnet test $PROJECT_PATH
Handle failures:
quickdup -path $SOURCE_DIR -ext .cs -select 0..20 -min 2 -exclude ".g.,.generated."
If new duplications are found:
/quickdup for refactoring patterns)dotnet format $PROJECT_PATH
Confirm all checks passed:
Only after ALL checks pass, create the pull request.
Evaluate and improve an API by inventing real, valuable tasks, attempting them through the public API, measuring the usefulness of its features and data, and turning failures into verified fixes or evidence-backed retirement proposals. Use when asked to dogfood, audit, rationalize, improve, simplify, or find value in an API; assess whether endpoints or features produce useful information; or decide what to keep, fix, combine, document, or retire.
Keep iterating on the next logical step in a project until a clear stop condition is reached. Use when the user says `/continue-loop`, asks to "keep going", "continue iterating", or wants Codex to repeatedly choose the highest-leverage next task, execute it, verify it, and then continue. Good for open-ended cleanup, refactoring, polish, debt burn-down, and project advancement where the next step should be discovered from the current repo state instead of handed over explicitly.
Find and explain churn hotspots and unstable code clusters in a git repo. Goes beyond a flat "most-edited files" list — auto-detects clusters by directory, by filename stem (foo.go + foo_test.go), and by co-change (files that change together) — then classifies each cluster (unstable / under-development / buggy / tightly-coupled / spec-shifting) and explains *why* it's a problem. Trigger whenever the user asks about churn, hotspots, unstable code, files that change a lot, refactoring candidates, technical debt hotspots, "what's a mess", "/hotmess", or any combination of folder + time window where they want insight rather than just numbers. Auto-detects code files when no extension is given.