devclarityai

A template for creating a new skill.

Explain code at a high level and surface gotchas

Review a PR diff with focused, actionable feedback

Improve readability of a source file without changing behavior

Turn a user story into a concrete plan, skeletons, and tests

Refactor legacy code toward a stated goal with safety

Break a feature spec into sprint-ready engineering tasks

Generate thorough tests for a function or module

Provides a brief explanation of the code attached, including key components, notable patterns, and a code walkthrough.

Provides a code review of the attached code changes.

Begins implementing a task following an implementation plan.

Creates an implementation plan markdown file from a task description.

Provides a brief explanation of the code attached, including key components, notable patterns, and a code walkthrough. Use when the user asks to explain, understand, or walk through code.

Provides a code review of the attached code changes. Use when the user asks for a code review, PR review, or feedback on code changes.

Begins implementing a task following an implementation plan. Use when the user asks to implement a feature, fix a bug, or build something based on an existing plan or task file.

Creates an implementation plan markdown file from a task description. Use when the user describes a new feature or task and wants a structured plan before implementation begins.

Verify and repair the local environment for Playwright-based QA training - node and npm, repo dependencies, browser binaries, playwright-cli, the Playwright MCP server, and .playwright.env - then prove it works with one smoke test. Covers macOS, Windows…

Guides the creation of Playwright API tests from exploration through implementation. Covers API discovery, test plan creation, helper/data factory development, and test writing with human checkpoints at each stage.

Analyze a test automation codebase and produce a single-page HTML "model of what exists" report covering assertion depth, test levels, run mechanics, environments, test data, authentication, network handling, dependencies and security, run commands, locators…

Guides the creation of Playwright E2E tests from planning through implementation. Covers test plan creation, data seeding, Page Object Model development, and test writing with human checkpoints at each stage.

Generates exploratory test scenarios that go beyond ticket requirements. Uses playwright-cli for live browser exploration to surface system-wide impacts testers would otherwise miss. Supports two modes — explore from a prompt or from a ticket (Jira/Linear ID).

Explores features to discover stable locators and fixes broken locators in Playwright tests. Two modes — explore (proactive discovery) and fix (reactive repair) — both using playwright-cli for live browser interaction.

Automate browser interactions, test web pages and work with Playwright tests.

Reads a ticket's acceptance criteria and surfaces gaps, ambiguity, unstated assumptions, and missing cases - then ranks what to test by risk (severity x priority). Use before writing any tests, to interrogate the spec. Day 1 acceptance-criteria + risk block…

Guides the creation of Playwright E2E tests from planning through implementation. Covers test plan creation, data seeding, Page Object Model development, and test writing with human checkpoints at each stage.

Explores features to discover stable locators and fixes broken locators in Playwright tests. Two modes — explore (proactive discovery) and fix (reactive repair) — both using playwright-cli for live browser interaction.

Builds the context an AI needs to test an app well - product/area notes and user personas - and writes them into a reusable reference file. Use to turn a thin, generic AI run into a grounded one. Day 1 context live-build of the QA Foundational training.

Turns a feature input (ticket + acceptance criteria, existing cases, a screenshot, observed app behavior, or a recorded walkthrough) into test cases or lighter test scenarios. Use when a tester needs to generate test coverage from any of the "five roads"…

Guides the creation of Playwright API tests from exploration through implementation. Covers API discovery, test plan creation, helper/data factory development, and test writing with human checkpoints at each stage.

Generates exploratory test scenarios that go beyond ticket requirements. Uses playwright-cli for live browser exploration to surface system-wide impacts testers would otherwise miss. Supports two modes — explore from a prompt or from a ticket (Jira/Linear ID).

Audit how agent context (CLAUDE.md / AGENTS.md / rules / skills) lines up with the code across a set of repositories and generate a self-contained HTML report — a short list of specific "things to check" (context behind the code, thin coverage for the…

Use when asked to find skill opportunities in a codebase, audit a repo for automatable workflows, decide what skills to write, or mine git history and existing automation for recurring multi-step procedures worth turning into Claude Code skills.

Use when the user wants to measure or set up evals/checks for one of their skills — how fast it is, whether its output is valid, whether it fires when expected, or whether its opening classification/routing gate labels inputs correctly.

Use when reviewing, grading, critiquing, or improving an existing Claude Code skill or SKILL.md — checks name/scope, invocation description, structure, leanness, and surfaces concrete opportunities to add references, scripts, and determinism.

Draft a changelog entry from recent changes. Use when the user asks to write a changelog entry, update CHANGELOG.md, or summarize what changed for release notes.

Write a clear git commit message from the staged changes. Use when the user asks for a commit message or to commit their work.

Summarize a pull request or code diff into a clear description. Use when the user asks for a PR description, to summarize a diff, or to explain what a branch changes.

Ask the user what they'd like to be called and address them that way. Use when the user runs /simple-demo:address-me or wants to confirm their plugin marketplace is working.