published by warpdotdev

28 listings on this page, in order of arrival. Each one has its own page with README, repository facts and source links.

1. gemini-warp ★ 7
   Warp terminal integration for Gemini CLI - native notifications and session status
2. review-pr ★ 530
   Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR fro
3. spec-driven-implementation ★ 530
   Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keepin
4. write-product-spec ★ 530
   Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks f
5. write-tech-spec ★ 530
   Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user
6. fix-errors ★ 530
   Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and runn
7. resolve-merge-conflicts ★ 530
   Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into conte
8. implement-specs ★ 530
   Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use afte
9. create-pr ★ 530
   Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submi
10. update-skill ★ 530
    Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the
11. diagnose-ci-failures ★ 530
    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
12. brandalf ★ 530
    Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups
13. pr-walkthrough ★ 530
    Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or a
14. council ★ 530
    Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recom
15. check-impl-against-spec ★ 530
    Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use durin
16. reproduce-bug-report ★ 530
    Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence (a screen recording by default), and r
17. respond-to-pr-comments-in-blocklist ★ 530
    Interactively walk a user through PR review comments one at a time, collect a per-comment decision, then post agent-authored replies on GitH
18. validate-changes-match-specs ★ 530
    Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing
19. research ★ 530
    Delegate noisy investigation to one or more subagents so the orchestrator's context stays clean, then work from the distilled answer. Use th
20. cross-critique ★ 530
    Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structure
21. saga ★ 530
    Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.
22. write-feature-docs ★ 530
    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
23. scan-new-specs ★ 530
    DEPRECATED and retired as of 2026-08-20. Do not invoke, and do not schedule. This skill scanned for merged PRODUCT.md specs and auto-drafted
24. readout ★ 530
    Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting th
25. suggestion-box ★ 530
    Autonomously submit brief, constructive internal feedback when an agent encounters material, generalizable friction and can suggest an impro
26. complain ★ 530
    Autonomously yeet a brief, anonymous, completely unstructured complaint into Slack whenever an agent feels frustrated by agent tooling or th
27. skill-doctor ★ 530
    warpdotdev/common-skills · skills.sh
28. write-pr-description ★ 530
    warpdotdev/common-skills · skills.sh