gh-fix-ci by davila7/claude-code-templates
npx skills add https://github.com/davila7/claude-code-templates --skill gh-fix-ci使用 gh 定位失败的 PR 检查,获取 GitHub Actions 日志以分析可操作的失败,总结失败片段,然后提出修复计划并在明确批准后实施。
plan 技能来起草和批准修复计划。前提条件:确保 gh 已通过身份验证(例如,运行一次 gh auth login),然后以提升的权限(包含 workflow/repo 范围)运行 gh auth status,以便 gh 命令成功执行。如果沙盒环境阻止 gh auth status,请使用 sandbox_permissions=require_escalated 重新运行。
repo:仓库内的路径(默认为 )广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
.pr:PR 编号或 URL(可选;默认为当前分支的 PR)gh 身份验证python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"--json。gh auth login 后,以提升的范围(workflow/repo)运行 gh auth status。sandbox_permissions=require_escalated 重新运行该命令以允许网络/密钥环访问。gh pr view --json number,url。python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"--json 以获得机器友好的输出。gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
gh 报告的可用字段重新运行。detailsUrl 中提取运行 ID 并运行:
gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headShagh run view <run_id> --loggh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"detailsUrl 不是 GitHub Actions 运行,则将其标记为外部检查并仅报告 URL。plan 技能起草一个简洁的计划并请求批准。gh pr checks 以确认。获取失败的 PR 检查,拉取 GitHub Actions 日志,并提取失败片段。当失败仍然存在时以非零状态退出,以便在自动化中使用。
使用示例:
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json"python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40每周安装量
150
仓库
GitHub 星标数
22.6K
首次出现
2026年1月21日
安全审计
安装于
claude-code124
opencode113
gemini-cli110
cursor106
antigravity98
codex98
Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.
plan skill for drafting and approving the fix plan.Prereq: ensure gh is authenticated (for example, run gh auth login once), then run gh auth status with escalated permissions (include workflow/repo scopes) so gh commands succeed. If sandboxing blocks gh auth status, rerun it with sandbox_permissions=require_escalated.
repo: path inside the repo (default .)pr: PR number or URL (optional; defaults to current branch PR)gh authentication for the repo hostpython "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"--json if you want machine-friendly output for summarization.gh auth status in the repo with escalated scopes (workflow/repo) after running gh auth login.sandbox_permissions=require_escalated to allow network/keyring access.gh pr view --json number,url.python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"--json for machine-friendly output.Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.
Usage examples:
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --jsonpython "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40Weekly Installs
150
Repository
GitHub Stars
22.6K
First Seen
Jan 21, 2026
Security Audits
Gen Agent Trust HubWarnSocketPassSnykWarn
Installed on
claude-code124
opencode113
gemini-cli110
cursor106
antigravity98
codex98
gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
gh.detailsUrl and run:
gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headShagh run view <run_id> --loggh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"detailsUrl is not a GitHub Actions run, label it as external and only report the URL.plan skill to draft a concise plan and request approval.gh pr checks to confirm.