Use when the agent must report a newly discovered defect, implement an approved bug fix, or harden regression coverage and documentation around a known bug. This skill enforces repository-aware bug intake, failing confirmation tests before fixes, scoped verification, documentation updates when warranted, and a structured resolution report.
Analyze a repository before engineering work begins and produce a concise context bundle covering structure, entry points, dependencies, tests, conventions, and likely risk areas. Use when the user asks for a codebase overview, wants a Phase 0 understanding pass, or when another skill would benefit from a grounded map of an unfamiliar project before implementation, review, or refactoring.
Audit the active working context and remove token noise before deeper implementation, review, or planning work. Use when Codex has accumulated too many files, notes, logs, prior summaries, or reference documents and needs to decide what to keep, drop, condense, or defer. Especially useful after broad codebase sweeps, large documentation reads, debug-log dumps, multi-skill handoffs, or whenever context relevance, signal density, or token efficiency has become uncertain.
Requirements-analysis skill for Cypress planning and implementation. Use when the agent needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.
CI and delivery skill for Cypress automation. Use when the agent needs to design, debug, or optimize Cypress execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.
Automates browser interactions for web testing, form filling, screenshots, and data extraction using cypress-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser sessions, or generate test code.
Migration skill for moving existing UI automation to Cypress. Use when the agent needs to translate Playwright or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
Central entrypoint for broad or ambiguous Cypress requests. Use when the agent needs to classify the user's testing goal, choose the right Cypress subskill, and move from intent to implementation, planning, documentation, execution, or reporting without unnecessary menu-driven back-and-forth.
Test-architecture skill for Cypress page objects, fixtures, helpers, and custom commands. Use when the agent needs to decide whether to introduce a Page Object Model, how to structure page objects, and how to separate browser state, UI behavior, and stateless utilities cleanly.
Use when you need an authorized, non-destructive security review of repos, APIs, and cloud apps. Trigger for OWASP reviews, dependency/secret audits, scanner consolidation, and security reports. Use for AppSec triage. Do NOT use for offensive exploitation or unauthorized testing.
Decide which diagrams to draw, what to put in them, and which tool fits — Mermaid, PlantUML, or draw.io. Plans content from code, requirements, schemas, or ADRs and hands off rendering to a sister skill (pretty-mermaid, PlantUML-skill, or drawio-skill). Do NOT render directly.
Design, review, and retrofit human-oversight controls for autonomous agent systems with pause, review, resume, reject, or halt behavior. Use for EU AI Act Article 12/14 logging, human handovers, typed review-decision contracts, reviewer reports, timeout/escalation rules, or critiques of unsafe approval flows.
Use when the agent needs to derive JUnit 5 test scenarios from requirements, code, or existing test case definitions such as TDD, BDD, and plain-text specifications.
Use when the agent needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.
Use when the agent needs to run JUnit 5 tests through Maven, Gradle, or the Console Launcher, configure CI pipelines, manage tags and reports, or debug environment-specific execution issues.
Use when the agent needs to create, run, debug, evaluate, refactor, or correct JUnit 5 tests across component, integration, slice, repository, service, smoke, or regression scenarios.
Use when the agent needs to create, review, or debug JUnit 5 extensions, custom annotations, lifecycle callbacks, parameter resolvers, or reusable execution hooks.
Use when the agent needs to migrate tests from JUnit 3 or JUnit 4 to JUnit 5, replace runners and rules, reduce Vintage usage, and preserve behavioral compatibility during modernization.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.