@warpdotdev

reproduce-bug-report launches oz cloud agents with computer use to faithfully exercise ui bugs, capture ordered screenshots, and report reproduction status with environment detail and artifact paths. handles multi-variant testing and version-matching constraints.

fix-errors guides resolution of compilation errors, linting failures, and test breakage in the warp rust codebase, with specific attention to wasm target constraints and presubmit validation workflows.

saga orchestrates autonomous, spec-driven development for medium-to-large features by delegating work to subagents via tightly-defined task contracts. human approval gates phase transitions and resolves genuine blockers only.

validate-changes-match-specs compares branch implementations against product, technical, and security specs by extracting commitments, inspecting code and tests, then guiding users through material mismatches one-by-one or in batch mode.

check-impl-against-spec validates pr implementations against spec commitments during review, extracting concrete requirements and flagging material mismatches while tolerating harmless implementation variations.

council orchestrates parallel subagent investigation of judgment-heavy decisions using model diversity and assigned perspectives, then synthesizes findings into a single recommendation.

guides users through actionable pr review comments with fetching, per-comment decision collection, code application, and approval gates before posting or resolving threads.

cross-critique routes independent proposals back to their authors for structured peer review, surfacing hidden assumptions and failure modes before synthesis. useful for contested decisions where multiple reasonable approaches exist.

resolve-merge-conflicts provides structured extraction of conflict metadata and hunks across unresolved files, prioritizing context-efficient inspection over full-file loading.

review-pr evaluates pull request diffs against correctness, security, and error handling criteria. it writes structured feedback to review.json without posting to github, with optional spec validation and local security guidance integration.

update-skill guides creation and updating of skill definitions via SKILL.md files, establishing repository structure and frontmatter conventions without specifying execution mechanics or failure modes.

pr-walkthrough generates a static four-view d3 canvas (system overview, data flow, code dependency, user action) to orient reviewers without requiring a dev server or build step. scope and output are clearly specified but execution steps remain vague.

brandalf directs users to an external brand guidelines site as the canonical reference for warp and oz asset creation, but provides no actionable procedure, decision logic, or integration steps.

Scan warpdotdev/warp and warp-server for recently merged PRODUCT.md specs that don't yet have a corresponding docs PR in warpdotdev/docs. When a complete spec…

Draft a complete documentation page for a new Warp feature from its PRODUCT.md and/or TECH.md spec. Use when an engineer has written a spec and needs to…

Delegate noisy investigation to one or more subagents so the orchestrator's context stays clean, then work from the distilled answer. Use this skill whenever…

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…

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…

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…

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…

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,…

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…

Optimize for search engine visibility, ranking, and AI citations. Use when asked to improve SEO, optimize for search, fix meta tags, add structured data, or…