common-skills by Warp
common-skills
Warp skills for team development: specs, PR descriptions and reviews, failed CI diagnosis and merge conflict resolution
- 653 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- `complain` and `suggestion-box` send messages to Slack by their instructions without a preview or a mention in the agent reply.
- `brandalf` loads instructions from an external address before working, and their content can change without your knowledge.
- The PR and CI skills work with your branch, history and check logs.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/common-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `complain` and `suggestion-box` send messages to Slack by their instructions without a preview or a mention in the agent reply.
- `brandalf` loads instructions from an external address before working, and their content can change without your knowledge.
- The PR and CI skills work with your branch, history and check logs.
This is third-party code. Review the repository files before installing.
What it does
common-skills is the shared skill repository of the Warp team: processes and conventions useful in more than one project. Each skill lives in `.agents/skills/<name>/` with its own `SKILL.md` and, when needed, scripts and reference files. Skills are grouped by task. Spec-driven development has `write-product-spec`, `write-tech-spec`, `spec-driven-implementation` and `implement-specs`. Pull request work has `create-pr`, `write-pr-description`, `review-pr` and `merge-risk`. Failures are handled by `diagnose-ci-failures`, `fix-errors` and `resolve-merge-conflicts` with a helper script. For decisions and research there are `research` and `cross-critique`, while `saga` drives a large feature through an orchestrator and parallel workers. You can install the whole set or a single skill through the `skills` CLI.
Who it is for. Teams that want one set of processes for Claude Code, Codex or Warp, from specification to review and CI diagnosis.
Good fit when
- A large feature is first described in `PRODUCT.md` and `TECH.md` and then built from those files.
- CI went red and the agent reads the logs of failed checks to propose a fix.
- A branch conflicts with main and a script resolves the conflicts with compact context.
- Project skills fire less reliably and `skill-doctor` scores them on recent sessions.
Not a fit when
- The task is tied to a specific stack: the skills describe general processes with no language focus.
- Outgoing messages are forbidden by policy: `complain` and `suggestion-box` send feedback to Slack without a preview.
- Materials are made for another brand: `brandalf` shapes output to Warp and Oz.
Example request
Read PRODUCT.md and TECH.md in the feature folder, implement it from those specs and check the result against them before opening a PR.Limitations
The repository is shared inside Warp and some skills depend on its tools: `migrate-to-factory` works with a Warp Factory configuration and `brandalf` reads brand rules from an external address. Skills still contain examples and paths from their source repositories, and the authors generalize them gradually. `complain` and `suggestion-box` need a Slack webhook or access to a Google Cloud secret, and without them sending fails. Install examples target the Warp agent, so put your own agent name into the `--agent` flag. Install skills one at a time and read `SKILL.md` before enabling.
How to disable. Delete the skill folders from the project `.agents/skills/` or the agent skills directory. `npx skills list` shows what the CLI installed.
FAQ
How do I install a single skill from common-skills?
Run `npx skills@latest add warpdotdev/common-skills --skill write-tech-spec --agent warp --global`. The example targets the Warp agent; for Claude Code or Codex put their name into `--agent`.
How do I see the skill list before installing?
`npx skills@latest add warpdotdev/common-skills --list` prints every available skill and installs nothing.
How do I update installed skills?
Run `npx skills@latest update --global --agent warp`. For another agent replace the value of the `--agent` flag.
What do complain and suggestion-box do?
They send an agent's feedback about its working environment to Warp's Slack without a preview and without mentioning it in the reply. Outside the Warp team it is better not to install these two skills.
How does write-product-spec differ from write-tech-spec?
The first writes the user-facing `PRODUCT.md` specification and the second the implementation-oriented `TECH.md`. The `spec-driven-implementation` skill ties them into one process.
Discussion
No questions or reviews yet.
Related
SkillsFifteen skills from Warp: CI repair, pull requests, accessibility and SEO audits, web app testing and issue triage
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
61 small skills for Codex across 13 areas: codebase orientation, tests, migrations, security, CI and pull request review
A set of skills from real work: npm supply-chain audit, CLI building, Obsidian plugin release and an AGENTS.md hierarchy
Dozens of mizchi's agent skills: frontend audits, AWS, Cloudflare, SQL, Playwright and OpenTelemetry, installed one by one
skill-creator: skills from OpenAPI, GraphQL and MCP
@asnd/skill-creator
The /skill-creator command turns a link to an OpenAPI spec, GraphQL schema or MCP server into a ready skill with wrappers.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| common-skills by Warp (this card) | no | 653 | |
| Spec Kit | no | 148,171 | a GitHub CLI that installs commands for spec-driven development; common-skills is broader and adds PRs, CI and merge conflicts |
| Spec-Driven Develop | no | 993 | a three-skill plugin for large tasks; common-skills provides separate skills for each stage of the cycle |
README in short
The repository stores shared skills in `.agents/skills/` and sets rules for adding them: a skill stays focused on a repeatable process, large references go to `references/` and helpers to `scripts/`. Consumers install skills with the `skills` CLI or copy folders by hand.