fix-ci
Find failing PR checks, inspect logs or external check links, and apply focused fixes
- License 许可
- MIT
- 最近更新
- 2026-10-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- fix-ci
- description
- Find failing PR checks, inspect logs or external check links, and apply focused fixes
03 SKILL.md 正文
Fix CI
Trigger
Branch or PR CI is failing and needs a fast, iterative path to green checks.
Workflow
- Resolve the active PR and inspect
gh pr checks --json name,bucket,state,workflow,link. - Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.
- Apply the smallest safe fix.
- Push, re-check the PR check set, and repeat until green.
Guardrails
- Fix one actionable failure at a time.
- Prefer minimal, low-risk changes before broader refactors.
- Keep
gh pr checksas the source of truth for overall PR CI state.
Output
- Primary failing job and root error
- Fixes applied in iteration order
- Current CI status and next action
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.