用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/drmoisan/drm-copilot --skill ci-workflows命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | ci-workflows |
| description | GitHub Actions PowerShell workflow authoring rules. |
Source: legacy Claude rule ci-workflows.
This rule governs GitHub Actions workflow steps that run PowerShell (pwsh). It exists because a pwsh step that intentionally invoked a failing nested command left $LASTEXITCODE == 1 after its verification logic had already succeeded, leaking a failure to GitHub Actions even though the step's intent was satisfied (issue #26, PR #30).
A workflow step whose run: block intentionally invokes a command expected to fail — for example a negative-path self-validation that asserts a gate catches a synthetic regression — MUST not allow the residual non-zero exit code to propagate to GitHub Actions.
For any such step, the run: block MUST do one of the following:
& ./some-tool --expect-failure
$LASTEXITCODE = 0
if ($verificationSucceeded) { exit 0 } else { exit 1 }
A pwsh step terminates with the exit code of the last external command unless the script explicitly resets it or calls exit. Negative-path verification steps therefore require an explicit reset or explicit exit 0.
$LASTEXITCODE from an intentionally-failing nested command causes a passing verification to report failure.run: block, so this defect is invisible to local feature-review. This textual rule is the artifact local review cites when reading workflow YAML.pwsh steps with deliberately-failing nested commands.modified-workflow-needs-green-run (see .agents/skills/feature-review-workflow/SKILL.md) requires a green workflow run against the branch head before a workflow change can merge, which exercises the exit-code path on the runner.run: block uses shell: pwsh (or the repo default pwsh) and intentionally invokes a failing nested command.