菜单
Port fixes from the SurveyController desktop repo into SurveyCore without copying GUI noise. Use when a user mentions an upstream commit, release, parser breakage, provider regression, or asks whether a desktop-side fix also needs to land in SurveyCore.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | survey-upstream-port |
| description | Port fixes from the SurveyController desktop repo into SurveyCore without copying GUI noise. Use when a user mentions an upstream commit, release, parser breakage, provider regression, or asks whether a desktop-side fix also needs to land in SurveyCore. |
Read upstream changes, strip GUI noise, and map the useful part into SurveyCore modules.
provider protocol: request params, signatures, cookies, parsing selectors, submit payloads.question semantics: new question types, option metadata, jump/display logic, psychometric handling.runtime/config: config fields, defaults, validation, scheduler behavior.desktop-only: UI, tray, window state, local packaging. Usually ignore these for SurveyCore.internal/providers/<provider>/.internal/providers/providerutil/.internal/questions/, internal/config/, internal/execution/, or internal/models/.internal/network/httpclient/ or internal/network/proxy/.internal/api/, docs/sdk/, README.md, and tests.references/module-map.md before deciding file targets.references/provider-checklist.md.scripts/upstream_diff.ps1 to summarize upstream diffs when the user provides a commit-ish.scripts/make_regression_plan.ps1 after mapping the affected SurveyCore files.Keep SurveyCore HTTP handlers, response schemas, SDK docs, README examples, and tests aligned. Use when routes, request bodies, error codes, response fields, pagination behavior, or config-generation output change.
Keep SurveyCore runtime configuration contracts aligned across models, defaults, validation, execution shaping, example configs, SDK schemas, and tests. Use when config fields, defaults, validation rules, or question-entry semantics change.
Scaffold a new SurveyCore provider capability with the right package split and wiring. Use when adding a new provider, a new parser path, a new answer-builder capability, or a provider-specific question behavior without spreading platform branches across shared packages.
Build and run the smallest credible regression plan for SurveyCore provider changes. Use when parser, answer builder, submitter, proxy, scheduler, or provider detection code changes and you need proof that one platform fix did not break the others.