claude

webdev

Portable web dev workflow that auto-detects your stack (JS/TS, PHP). Branch, plan, test, commit, open and review PRs — beginner-safe defaults, power-user overrides via .claude/webdev.json.

1 on GitHubby Jabal Torresv1.8.0MITupdated 1 month ago
/

Plugin webdev from marketplace webdev-skills in jaballer/claude-webdev-skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (20)

  • commit

    Commits completed work the right way — staging the right files, running tests and the formatter first, a hostile pre-push self-review, a conventional-commits message, push, and (by default) opening a PR. Use when the user says "commit", "let's commit", "commit these changes", "I'm ready to commit",

  • detect-stack

    Resolves the project's toolchain — package manager, test runner, formatter/linter, framework, and dev/run command — so other webdev skills issue the right commands on any stack. Auto-detects JS/TS and PHP; every other stack is supported through an explicit .claude/webdev.json override. Use at the st

  • explain-codebase

    Orient someone in an unfamiliar codebase — what it is, the stack, where things live, the entry points, how to run/test/build it, and where to start reading. Use when the user says "explain this codebase", "help me understand this project", "give me a tour", "what is this", "where do I start", "how d

  • fix-bug

    Drives a bug fix end to end with the reproduce → failing test → fix discipline. Use when the user reports broken behavior: "fix this bug", "X is broken", "X stopped working", "users are seeing Y", pastes an error/stack trace, or points at a defect issue ("fix issue #N"). Bug-shaped work differs from

  • fix-ci

    Triage and fix a failing CI check on a PR or branch. Use when the user says "CI is failing", "the build is red", "checks failed", "fix the pipeline", "why did CI fail", or any time a PR's checks are red after a push. Reads the failing run's logs via gh, finds the first real error, classifies the fai

  • merge-pr

    Merges a pull request the safe way — verify approvals, green checks, and resolved threads first, pick the repo's merge method, merge, then clean up via sync-main. Use when the user says "merge it", "merge the PR", "land it", "squash and merge", "it's approved — merge", or after /webdev:review-pr rep

  • new-branch

    Creates a properly-named git branch before starting any new work. Use at the start of every coding session, feature, bug fix, or task. Trigger whenever the user mentions starting something new, working on an issue, fixing a bug, or any time work is about to begin and no feature branch exists yet. If

  • new-feature

    Drives a new piece of work from start to finish — branch, pre-implementation inventory (when warranted), implementation, tests, and commit/PR — by chaining the atomic webdev skills. Use when building any new feature, endpoint, page, component, or integration. Trigger when the user says "add a featur

  • open-pr

    Opens a GitHub pull request with a structured, reviewable body. Use whenever the user says "open a PR", "create the PR", "push and open a PR", "ship it", or any time work is committed and pushed to a working branch but the PR isn't open yet. Also invoked automatically as the final step of /webdev:co

  • plan-inventory

    Produce a written inventory of what already exists and could break BEFORE writing any code, for non-trivial work. Use whenever the task involves consolidating / splitting / renaming / deleting routes, components, exports, or services with multiple call sites; reusing existing shared infrastructure (

  • post-merge-review

    Deep-dive review of a single specific merged PR to catch issues that slipped through code review — bugs, missing tests, inconsistencies, doc gaps. Use when the user wants to review a particular PR after merge or spot-check a specific merge. Trigger on "review PR #123", "check what that PR changed",

  • qa-review

    Broad QA review of recently merged functionality (not one specific PR). Use when the user wants to review recent work, smoke-test merged features, or audit the latest additions. Trigger on "review recent changes", "QA the latest merge", "smoke test", "review what was merged", "anything need fixing?"

  • review-pr

    Address and resolve GitHub pull request review comments end to end. Use whenever the user shares a PR URL and asks to "address comments", "fix the feedback", "resolve the review", "handle the bot comments", or pastes a PR URL with "fix this PR". Handles the full loop: read comments → verify each cla

  • run-tests

    Runs the project's test suite at the smallest scope that proves the change. Use when the user asks to "run tests", "check tests", "make sure tests pass", or before committing or opening a PR. Also trigger automatically after code changes that could affect existing functionality. Resolves the test co

  • safe-edit

    Guardrails for risky operations — classify blast radius and reversibility, then confirm, back up, or proceed accordingly. Use before anything destructive or hard to undo: force-pushing, deleting files or branches, dropping/resetting a database, running migrations, bulk find-and-replace, rewriting gi

  • setup

    First-run setup for a project — detects the stack, scaffolds a CLAUDE.md and an optional .claude/webdev.json, and explains what it configured. Use when the user installs this plugin in a new project, says "set up webdev here", "configure this project", "get started", "initialize", or when other webd

  • ship-it

    The guided, beginner-friendly way to take a change from idea to merged PR. Same workflow as /webdev:new-feature, but it explains each step in plain language, confirms before anything irreversible, and assumes you're new to git, branches, and pull requests. Use when the user says "help me ship this",

  • sync-main

    Returns the local repo to a verifiably clean state on the latest default branch before starting the next task. Use after a PR is merged and deployed, when switching context between tasks, or any time you want to confirm the base is up to date and stale local branches are cleaned up. Trigger phrases:

  • verify

    Proves a change works by exercising the RUNNING app, not just the test suite — start the dev server, drive the changed behavior, observe the result. Use before committing user-facing work (UI, routes, forms, emails-to-preview, API responses), or when the user asks "does it actually work?", "check it

  • watch-pr

    Polls a pull request on a fixed interval until it reaches a terminal state — approved, changes-requested, merged, or closed — then either notifies you or hands off to /webdev:merge-pr. Use when the user says "watch the PR", "poll PR #X", "tell me when it's approved", "keep checking the PR", "let me

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.

2 commands

alibaba/open-code-review 50,068

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

promptfoo

claudecodex

Connect providers and targets, write eval suites, and set up or run red team scans with promptfoo

4 skills

promptfoo/promptfoo 27,115

Maintain webdev?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted