Agent Skills
› openai/plugins
› circleci-builds
circleci-builds
GitHub用于快速诊断和修复 CircleCI 构建失败。通过日志定位根因，分类问题类型（如配置、依赖或测试回归），实施最小化安全修复，并验证结果。遵循严格规范，避免掩盖确定性故障，确保修复精准且风险可控。
Trigger Scenarios
用户请求调查失败的 CircleCI 作业
需要排查不稳定的流水线
从日志中识别根本原因
实施配置文件或构建代码的最小修复
Install
npx skills add openai/plugins --skill circleci-builds -g -y
SKILL.md
Frontmatter
{
"name": "circleci-builds",
"description": "Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths."
}
CircleCI Builds
Overview
Use this skill to turn failing CircleCI pipelines into actionable fixes with clear evidence. Prioritize fast root-cause isolation, minimal safe patches, and explicit validation criteria.
Read references/transient-vs-deterministic.md when deciding whether a failure should be fixed in code/config, retried, mitigated with rerun behavior, or reported as external/transient.
Read ../config/references/test-results-and-splitting.md when the failure involves missing test metadata, flaky test reruns, test splitting, or JUnit XML setup.
Inputs To Gather
- Failing pipeline/workflow/job identifier
- Branch and commit SHA
- First failing step and key log lines
- Whether rerun on same commit reproduces failure
Workflow
- Identify the primary failing signal.
- Record the first failing job and step, not every downstream failure.
- Classify issue type.
- Config syntax/reference issue
- Environment/toolchain mismatch
- Dependency/cache issue
- Test or build regression
- External/transient failure
- Apply the smallest viable fix.
- Patch only files tied to confirmed root cause.
- Keep workaround scope narrow.
- Validate.
- Run highest-signal local checks when possible.
- Define expected CircleCI success signals for the rerun.
- Report residual risk.
- Call out unverified assumptions and likely follow-up checks.
Guardrails
- Do not hide deterministic failures with blanket retries.
- Avoid mixing unrelated refactors into incident fixes.
- Treat external service outages as report-and-mitigate unless user asks for deeper redesign.
- Keep confidence levels explicit when logs are incomplete.
- Do not recommend automatic reruns or flaky-test workflows until the failure is classified as plausibly transient.
Output Contract
Provide:
- Failure summary (pipeline/workflow/job/step).
- Root-cause hypothesis with confidence.
- Applied changes with file list.
- Validation plan and expected pass signal.
- Remaining risk.
Version History
- 11c74d6 Current 2026-07-19 09:31
