respond-to-pr-comments-in-blocklist은(는) 무엇을 하나요?
PR 리뷰 댓글을 단계별로 처리하여, 필요 시 먼저 가져와 표시하고, 각 댓글에 대한 응답 결정을 수집하며, 요청된 수정 사항을 적용하고, 게시 전에 GitHub 회신 및 해결 상태를 미리 봅니다. 현재 브랜치의 PR 리뷰 댓글에 응답할 때 사용하세요.
PR 리뷰 댓글을 단계별로 처리하여, 필요 시 먼저 가져와 표시하고, 각 댓글에 대한 응답 결정을 수집하며, 요청된 수정 사항을 적용하고, 게시 전에 GitHub 회신 및 해결 상태를 미리 봅니다. 현재 브랜치의 PR 리뷰 댓글에 응답할 때 사용하세요.
이 스킬은 개발자가 현재 브랜치에 대한 PR 리뷰 댓글을 체계적으로 관리하고 응답할 수 있도록 지원합니다. 주요 기능으로는 리뷰 댓글을 자동으로 가져와 표시하고, 각 댓글에 대해 수락, 거절, 수정 등의 응답 결정을 내릴 수 있습니다. 사용자는 요청된 코드 수정 사항을 적용한 후, GitHub에 게시하기 전에 회신 내용과 댓글 해결 상태를 미리 볼 수 있어 실수를 방지합니다. Warp, Claude Code, Cursor 등 다양한 개발자 도구와 호환되며, SKILL.md 문서 기반으로 동작하여 일관된 워크플로우를 제공합니다. 이 스킬은 특히 여러 리뷰어의 피드백을 한 번에 처리해야 하는 복잡한 PR 검토 과정에서 생산성을 크게 향상시킵니다.
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/respond-to-pr-comments-in-blocklistInstalled? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
PR 리뷰 댓글을 단계별로 처리하여, 필요 시 먼저 가져와 표시하고, 각 댓글에 대한 응답 결정을 수집하며, 요청된 수정 사항을 적용하고, 게시 전에 GitHub 회신 및 해결 상태를 미리 봅니다. 현재 브랜치의 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.
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
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.
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.