Explorar skills

Use when defining a project's test approach, when choosing what gets tested at unit vs integration vs e2e level, when setting per-component coverage targets, when reviewing test quality, or when CI is slow / flaky and tests need a strategy reset.

Scope change workflow for modifying, adding, or removing requirements at any point during a build. Triggers on "change:" prefix, "I forgot to add", "actually I also want", "can we add", "remove X from scope", "I changed my mind about", "before we continue add", "one more thing", "I want to change the spec", "revert the X change". Handles new additions, removals, renames, backlog operations, and re

Use this skill during Phase 7 after a successful deployment to generate or update monitoring, logging, alerting, and observability artifacts that catch exceptions and issues in the deployed code. Produces platform-neutral scripts when no observability platform is configured, and integrates with Grafana/Datadog/CloudWatch via MCP when configured. Trigger after deploy, or when the user says "add mon

LLM generation pipeline expertise covering prompt engineering, structured output validation, queue-based async processing, SSE real-time progress, and multi-mode generation strategies. Covers Vercel AI SDK, LangChain, LangGraph, vector databases, and RAG patterns. Trigger keywords: AI generation, LLM pipeline, prompt engineering, structured output, Zod schema, BullMQ, SSE, RAG, vector database, em

Generates and maintains two changelog files from git tags, TASKS.md, DECISIONS.md, and feature folders. CHANGELOG.md at repo root is developer-facing in Keep a Changelog format with task IDs and decisions. CHANGELOG_CLIENT.md is plain English, grouped by "what you can now do", written like a product update — no task IDs or framework names. Version detection reads git tags first, then package.json

Use this skill to capture a human phase-gate sign-off through chat rather than requiring the user to manually edit the gate markdown file. Prompts the user with the artifact path, collects a work-item URL (REQ / ticket / CR) as the non-trivial acknowledgment, validates the URL shape against the ticket system configured in `config/tools.json`, and writes the signed gate file at `.claude/sdlc/gates/

Use this skill when the user runs /start, says "start", "enable the SDLC workflow", "I want to build", "I want to fix", "set up", "get started", or otherwise signals they want to activate or re-enable the SDLC workflow. Handles three distinct paths based on marker state — fresh install (opt-in activation), re-enable after suspension (reconciliation), and already-enabled (hand off to /plan). Power

Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or establishing evaluation frameworks.

Propose and write new tests for source files changed in the current session. Detects which functions are already covered and only proposes tests for gaps. Use when the user runs /qf-cover, asks to "add test coverage", asks to "write tests", reacts to the Qualflare hook suggestion, or explicitly invokes this skill. Pass --all to cover an entire file/directory regardless of what changed.

Autonomous browser testing agent for any web application. Discovers routes, tests pages, finds bugs via agent-browser (fast Rust daemon). Use when the user wants to test their web app, run browser tests, find UI bugs, do visual regression testing, or perform QA on any web application. Works with any app via browserhawk.config.json.

Skill de auto-reparo para gerar e manter arquivos CLAUDE.md. Ativa para criar, atualizar ou reparar CLAUDE.mds de um projeto, ou após erros, escaneando o código para gerar um CLAUDE.md raiz conciso.

Guide for writing expressive, behavior-focused tests following Vladimir Khorikov's testing principles. Apply when writing, reviewing, or renaming any test (unit, integration, e2e) in any programming language. Triggers: writing tests, creating test files, adding test cases, reviewing test names, 'test naming', 'rename tests', 'Khorikov', or any test creation task. Covers: naming conventions (plain