warpdotdev/check-impl-against-spec

Pull Request의 구현 사항을 spec_context.md의 사양 컨텍스트와 비교하여 중요한 불일치 사항을 review.json에 기록합니다. PR 리뷰 시 승인되었거나 저장소 사양 컨텍스트를 사용할 수 있을 때 사용하세요.

check-impl-against-spec란 무엇인가요?

이 스킬은 Pull Request의 코드 구현이 지정된 사양(spec)과 일치하는지 자동으로 검증합니다. PR의 변경 사항을 분석하여 spec_context.md 파일에 정의된 사양 컨텍스트와 비교한 후, 중요한 불일치(material mismatch) 사항을 찾아 review.json 파일에 구조화된 형태로 기록합니다. 주로 CI/CD 파이프라인이나 PR 리뷰 프로세스에서 사용되며, 승인된 PR이나 저장소에 사양 컨텍스트가 제공된 경우에 특히 유용합니다. 이 스킬을 통해 개발자와 리뷰어는 구현과 사양 간의 차이를 신속하게 파악하고, 리뷰 프로세스를 자동화하여 품질을 향상시킬 수 있습니다. warpdotdev 플랫폼과 함께 사용하도록 설계되었습니다.

지원 대상~Claude Code~Codex CLI~Cursor

npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/check-impl-against-spec

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

문서

check-impl-against-spec은(는) 무엇을 하나요?

Individual skills in this repo

This repo contains 16 individual skills — each has its own dedicated page.

warpdotdev/brandalf

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.

warpdotdev/council

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.

warpdotdev/create-pr

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.

warpdotdev/diagnose-ci-failures

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.

warpdotdev/fix-errors

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.

warpdotdev/implement-specs

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.

warpdotdev/pr-walkthrough

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.

warpdotdev/reproduce-bug-report

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.

warpdotdev/resolve-merge-conflicts

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.

warpdotdev/respond-to-pr-comments-in-blocklist

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.

warpdotdev/review-pr

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.

warpdotdev/spec-driven-implementation

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.

warpdotdev/update-skill

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.

warpdotdev/validate-changes-match-specs

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.

warpdotdev/write-product-spec

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.

warpdotdev/write-tech-spec

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.