warpdotdev/validate-changes-match-specs

브랜치나 풀 리퀘스트의 구현이 도입된 제품, 기술, 보안 및 관련 명세와 일치하는지 검증합니다. 명세 기반 변경 사항을 검토하거나 완료할 때 사용하며, 체크인된 명세와 구현 간의 불일치를 해결합니다.

validate-changes-match-specs란 무엇인가요?

이 스킬은 생성형 AI 에이전트(예: Claude Code, Cursor, Codex)가 브랜치나 풀 리퀘스트의 구현 결과가 프로젝트에 도입된 제품, 기술, 보안 및 관련 명세와 일치하는지 자동으로 검증할 수 있도록 설계되었습니다. 주로 명세 기반 변경(SDD, TDD) 워크플로우에서 사용되며, 개발자가 명세와 구현 간의 간극을 빠르게 파악하고 수정할 수 있도록 돕습니다. 이 스킬은 저장소 내 명세 파일과 구현 코드를 비교 분석하여 불일치를 보고하고, 해결 방안을 제시합니다. Warp, Cursor, Claude Code 등 다양한 개발 도구에서 사용할 수 있으며, 특히 코드 리뷰 과정에서 인간 검토자의 부담을 줄이고 일관된 품질을 유지하는 데 유용합니다. 구현이 명세를 완전히 반영하지 못한 경우, 누락된 기능이나 잘못된 동작을 구체적으로 지적하여 수정을 지원합니다.

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

npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/validate-changes-match-specs

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

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

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

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

ChatGPT Claude Gemini Grok Perplexity DeepSeek

문서

validate-changes-match-specs은(는) 무엇을 하나요?

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/check-impl-against-spec

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.

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/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.