AGENT SKILLS · ÉQUIPEMENT DE MISSION / warpdotdev

warpdotdev · Agent Skills

29 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

warpdotdev
Communauté

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.

installations
4
GitHub Stars
614
Mis à jour
18 oct.
warpdotdev
Communauté

write-feature-docs

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 produce a first-pass MDX draft for the warpdotdev/docs repo. Also handles features without specs by researching the codebase first. Invoke this skill whenever an engineer mentions writing docs for a feature, drafting a docs page, creating feature documentation, starting the eng-docs workflow, or converting a spec into documentation. Requires an

installations
4
GitHub Stars
614
Mis à jour
18 oct.
warpdotdev
Communauté

write-pr-description

Writes the body of a pull request - the summary, the repository template sections, and reviewer guidance such as a recommended reading order and focus areas. Use whenever drafting or revising a PR description, filling in a repository's PR template, refreshing a description that no longer matches the branch, or preparing a branch for review. Use it even when the user only says "open a PR", "put this up for review", or "write this up" without naming the description.

installations
4
GitHub Stars
614
Mis à jour
18 oct.
warpdotdev
Communauté

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.

installations
4
GitHub Stars
614
Mis à jour
18 oct.
warpdotdev
Communauté

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.

installations
4
GitHub Stars
614
Mis à jour
18 oct.