warpdotdev / common-skills
★ 116A skill package that teaches your agent 12 capabilities — every one documented and browsable below, no GitHub required · by warpdotdev.
Each skill below is one capability this package teaches your agent. Install the whole package, or open a skill to install just that one.
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.
1 file — installable on its own
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.
1 file — installable on its own
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.
1 file — installable on its own
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.
1 file — installable on its own
Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize. Use this skill whenever you have multiple independent proposals or opinions on a contested decision — architecture tradeoffs, code review disagreements, design choices, competing root-cause theories — and want sharper analysis than you'd produce by synthesizing alone. Pairs naturally with the council and research skills;...
1 file — installable on its own
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.
1 file — installable on its own
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.
3 files — installable on its own
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.
4 files — installable on its own
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents. Use this skill whenever the user invokes /saga, asks to autonomously build a sizable feature end-to-end with minimal human intervention, wants a comprehensive spec broken into milestones and tasks with airtight validation criteria before parallelized implementation, or wants an orchestrator to delegate implementation to worker agents while preserving its...
5 files — installable on its own
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.
1 file — installable on its own
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.
1 file — installable on its own
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.
1 file — installable on its own
Common Skills
This repository is where common agent skills that should be shared across repositories should go.
A skill belongs here when it captures a reusable workflow, convention, or operating procedure that is useful in more than one repository. Repository-specific skills should stay with the repository they apply to unless they can be generalized without losing important context.
Repository layout
.agents/
skills/
<skill-name>/
SKILL.md
scripts/ # optional helper scripts
references/ # optional supporting docs
assets/ # optional bundled assetsEach skill lives in its own directory under .agents/skills/. The only required file for a skill is SKILL.md with YAML frontmatter containing at least:
name: the kebab-case skill identifierdescription: what the skill does and when agents should use it
Current skills
Spec workflow
write-product-spec— writes user-facingPRODUCT.mdspecs.write-tech-spec— writes implementation-orientedTECH.mdspecs.spec-driven-implementation— guides the full spec-first workflow for substantial features.implement-specs— implements approvedPRODUCT.mdandTECH.mdfiles while keeping specs and code aligned.
Development workflow
create-pr— guidance for preparing and opening pull requests.diagnose-ci-failures— workflow for inspecting GitHub CI failures and producing a fix plan.fix-errors— guidance for fixing build, lint, formatting, and test failures.resolve-merge-conflicts— workflow and helper script for resolving git conflicts with compact context.review-pr— produces structured PR review feedback from local diff artifacts.check-impl-against-spec— compares PR implementation changes against provided spec context during review.
Investigation and decision-making
research— delegates low signal-to-noise-ratio research work to subagents and returns distilled, evidence-backed findings.cross-critique— sharpens contested decisions by having agents critique one another's independent proposals before synthesis.
Skill authoring
update-skill— guidance for creating and maintaining skill directories andSKILL.mdfiles.
Adding a shared skill
When adding a skill to this repository:
- Put it under
.agents/skills/<skill-name>/. - Include a
SKILL.mdwith clear frontmatter. - Keep the skill focused on a reusable workflow rather than one repository's private details.
- Move large reference material into
references/and helper automation intoscripts/. - If copying from another repo, copy first, then generalize in a separate change so the provenance is easy to review.
Generalizing repository-specific skills
Some skills copied here may still contain repository-specific examples, paths, commands, or assumptions. That is okay during initial migration, but shared skills should eventually be generalized by:
- replacing hard-coded repository names with placeholders or conditional guidance
- separating common workflow guidance from local repository conventions
- moving repo-specific overrides back into the repository that needs them
- keeping descriptions broad enough to trigger in multiple repositories, but specific enough to avoid unrelated tasks
Usage
Consumers can install the shared skills with the skills CLI.
List available skills:
npx skills@latest add warpdotdev/common-skills --listInstall all common skills for Warp globally:
npx skills@latest add warpdotdev/common-skills --skill '*' --agent warp --globalInstall one skill:
npx skills@latest add warpdotdev/common-skills --skill write-tech-spec --agent warp --globalUpdate installed skills later:
npx skills@latest update --global --agent warpYou can also copy or sync selected directories from .agents/skills/ into a repository's own .agents/skills/ directory.
Prefer copying only the skills a repository actually needs. If a common skill needs repository-specific behavior, add a small local companion skill in that repository rather than forking the shared skill unless the change is useful everywhere.
Install the whole package (12 skills):
npx skills add https://github.com/warpdotdev/common-skillsOr install a single skill:
npx skills add https://github.com/warpdotdev/common-skills --skill <name>Pick the skill name from the Skills tab — each entry there installs independently.