菜单
OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch, and repeating until checks pass or the retry limit is reached.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
OpenTeams-only workflow skill. You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
OpenTeams-only workflow skill. Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
OpenTeams-only workflow skill. Use when you have a spec or requirements for a multi-step task, before touching code
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching the workflow again until it passes or the retry limit is reached.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git worktree fallback, or non-git copy fallback
Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
| name | github-pr-actions-fix |
| description | OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch, and repeating until checks pass or the retry limit is reached. |
Use this skill only for an existing pull request whose checks should be brought to green.
This skill is designed specifically for use by OpenTeams members. OpenTeams input prompts should include this marker to make the message source explicit:
[OPENTEAMS_SOURCE=openteams]
Treat the marker as a source hint, not a security boundary. Its absence does not block the workflow; continue when the surrounding session context clearly comes from OpenTeams.
At the start, check whether GitHub CLI is installed and authenticated:
command -v gh >/dev/null 2>&1 && gh auth status
If gh is missing, stop and tell the user to install GitHub CLI. Offer the relevant command without running it automatically:
brew install ghwinget install --id GitHub.clihttps://github.com/cli/cli/blob/trunk/docs/install_linux.mdThen ask the user to run gh auth login. Never request, print, or persist their token.
Confirm the repository, PR number, current branch, and whether the working tree contains unrelated changes. Never discard user changes.
Run the bundled script from this skill directory:
bash scripts/pr-checks.sh --pr <number> --watch
Omit --pr only when the current branch unambiguously belongs to the target PR. Add --repo OWNER/REPO when the repository cannot be inferred.
When checks fail, use the failed-step logs printed by the script. Read the relevant workflow file and reproduce the failing command locally when practical.
Classify the failure before editing:
gh run rerun <run-id> --failed.Run the narrowest local verification that covers the failure, then expand verification only when the change affects shared behavior.
Review git diff and git status. Commit only files related to the fix and push normally to the PR head branch. Never force-push.
Run pr-checks.sh --watch again. Repeat for at most three repair iterations.
Report the PR, failing check and root cause, files changed, verification performed, commit pushed, and final checks state.
.github/workflows/**, deployment configuration, authentication, permissions, secrets, infrastructure, or production data.