diagnose-ci-failures은(는) 무엇을 하나요?
GitHub CLI를 사용하여 PR의 CI 실패를 진단하고, 오류 로그를 추출하며, 수정 계획을 생성합니다. 사용자가 CI 상태 확인, CI 이슈 조회, 테스트 실패 분류, PR 빌드 실패 조사를 요청할 때 사용하세요.
GitHub CLI를 사용하여 PR의 CI 실패를 진단하고, 오류 로그를 추출하며, 수정 계획을 생성합니다. 사용자가 CI 상태 확인, CI 이슈 조회, 테스트 실패 분류, PR 빌드 실패 조사를 요청할 때 사용하세요.
이 스킬은 개발자가 PR의 CI(지속적 통합) 실패를 신속하게 진단하고 해결할 수 있도록 돕습니다. GitHub CLI를 활용하여 PR의 CI 상태를 확인하고, 실패한 작업의 오류 로그를 추출한 후, 문제를 해결하기 위한 구체적인 계획을 생성합니다. 주로 CI 상태 확인, 테스트 실패 분류, 빌드 실패 조사와 같은 작업에 사용됩니다. 이 스킬은 GitHub Actions 등 CI/CD 파이프라인과 통합되어 있으며, CLI 기반으로 동작하므로 Cursor, Claude Code, Codex와 같은 터미널 에이전트 환경에서 특히 유용합니다. 실제 오류 메시지를 기반으로 한 실행 가능한 수정 단계를 제시하여 개발자의 디버깅 시간을 크게 단축시킵니다.
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/diagnose-ci-failuresInstalled? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
GitHub CLI를 사용하여 PR의 CI 실패를 진단하고, 오류 로그를 추출하며, 수정 계획을 생성합니다. 사용자가 CI 상태 확인, CI 이슈 조회, 테스트 실패 분류, PR 빌드 실패 조사를 요청할 때 사용하세요.
This repo contains 16 individual skills — each has its own dedicated page.
Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.
Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.