Claude Webdev Skills — Testing skill for Claude Code

Web Dev Workflow — Claude Code Skills

[](https://github.com/jaballer/claude-webdev-skills/actions/workflows/ci.yml)

A **stack-agnostic** set of [Claude Code](https://claude.com/claude-code) skills that give any web project a consistent, well-reasoned workflow: **branch → plan → test → commit → PR → review**. The skills auto-detect your toolchain (package manager, test runner, formatter, framework) so they work zero-config on a fresh Vite/Next/Laravel project — and let power users pin exact commands for any other stack via a small override file.

Built by [Jabal Torres](https://jabaltorres.com). Distributed as a Claude Code plugin.

Why

Most workflow skills are welded to one project's stack. These aren't. The *valuable* part of a workflow — when to branch, what to audit before writing code, how small a test run proves a change, how to self-review a diff before pushing — is the same whether you're on pnpm or Composer. This plugin keeps that structure and pushes the stack-specific commands down into a detection layer.

Install

Two separate steps — run each at Claude Code's main `/` prompt, one at a time:

1. **Add the marketplace.** Enter just the `owner/repo` when prompted for a source:

   /plugin marketplace add jaballer/claude-webdev-skills

2. **Install the plugin** from that marketplace:

   /plugin install webdev@webdev-skills

Don't paste both lines together. The first command opens an "Add Marketplace" dialog whose source field expects only `jaballer/claude-webdev-skills` — pasting the `/plugin install …` line into it produces an "is not a valid GitHub owner/repo" error.

Skills are then available namespaced as `/webdev:` (e.g. `/webdev:run-tests`), and Claude will also invoke them automatically based on what you ask for.

Updating

Editing this repo — or merging PRs into it — does **not** update your installe