cmd-fix-github-actions
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/fix-github-actions
/fix-github-actions
Agent skill wrapper for the Claude command .
/fix-github-actionsWhen the original command text references , , or named arguments, map them from the user's current request.
{{INPUT}}$1Agent skill wrapper for the Claude command .
/fix-github-actions当原始命令文本引用、或命名参数时,从用户当前请求中映射这些参数。
{{INPUT}}$1Command Instructions
命令说明
Fix GitHub Actions failures from recent workflow runs. Work in a git worktree under . Repeat up to $1 times (default 5).
.trees/修复最近工作流运行中的GitHub Actions失败问题。在目录下的git worktree中进行操作。重复最多$1次(默认5次)。
.trees/Process
流程
- Identify failures: then
gh run list --status=failure --limit=5for detailsgh run view <run-id> --log-failed - Create worktree: Branch from the failing ref into — create
.trees/fix-ci-<short-description>if missing.trees/ - Analyze and fix: Categorize failure (test/build/lint/deps/other), fix root cause in the worktree
- Verify locally when possible (e.g. ,
mix test,mix format --check-formatted)mix compile - Commit with descriptive message, push the fix branch
- Re-check: — if still failing, continue next iteration
gh run watch
- 识别失败: 执行,然后使用
gh run list --status=failure --limit=5查看详细信息gh run view <run-id> --log-failed - 创建工作树: 从失败的引用分支到——如果
.trees/fix-ci-<简短描述>目录不存在则创建.trees/ - 分析并修复: 对失败进行分类(测试/构建/代码检查/依赖/其他),在工作树中修复根本原因
- 尽可能本地验证(例如、
mix test、mix format --check-formatted)mix compile - 提交并添加描述性消息,推送修复分支
- 重新检查: 执行——如果仍然失败,继续下一次迭代
gh run watch
Rules
规则
- Fix root causes, not symptoms
- Do not skip/disable tests or modify CI workflow config without human approval
- Do not make unrelated changes
- Keep each commit focused on the specific failure being fixed
- 修复根本原因,而非表面症状
- 未经人工批准,不得跳过/禁用测试或修改CI工作流配置
- 不得进行无关更改
- 每次提交需专注于当前要修复的特定失败问题
Stop and ask for human review if
出现以下情况时停止并请求人工审核
- Same failure recurs 3+ times despite different fix approaches
- Failure is caused by secrets, credentials, or external infrastructure
- Fix requires significant architectural changes
- CI workflow YAML itself needs modification
- 尽管尝试了不同的修复方法,相同的失败仍重复出现3次以上
- 失败由密钥、凭证或外部基础设施导致
- 修复需要重大架构变更
- CI工作流YAML本身需要修改