Testing & Security

Security practices including secrets management, input validation, SSRF prevention, and production hardening. Use for security-sensitive code.

System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.

CQRS and Event Sourcing for auditability, read/write separation, and temporal queries.Triggers: CQRS, event sourcing, audit trail, temporal queriesUse when: read/write scaling differs or audit trail requiredDO NOT use when: simple CRUD - use architecture-paradigms first.

Workflow for capturing evidence and citations to create reproducible analysesand audit trails.Triggers: evidence capture, citations, reproducible analysis, audit trail,documentation, evidence logging, findings documentationUse when: conducting any review that needs evidence trails, creating auditdocumentation, ensuring reproducibility of analysesDO NOT use when: quick informal checks without documentation needs.DO NOT use when: structured output is the focus - use structured-output.Use this skill as foundation for all evidence-based review workflows.

Ensuring software correctness and reliability by writing automated tests, using quality assurance tools, and systematically debugging issues.

Incorporating security at every step of software development – writing code that defends against vulnerabilities and protects user data.

OWASP API Security Top 10 (2023) と Rust セキュリティベストプラクティス。脆弱性検出。Use when: セキュリティ、脆弱性、OWASP、認証、認可、監査を依頼された時。

Evaluate Clojure code via nREPL using clj-nrepl-eval. Use this when you need to test code, check if edited files compile, verify function behavior, or interact with a running REPL session.

TDD方法論に従ってテストを作成します。テスト対象コードの分析、AAA/Given-When-Thenパターンの適用、正常系・エッジケース・エラー系のカバレッジを確保します。「テストを書いて」「テストを作成」「単体テストを追加」などのリクエストで起動します。

A skill to automatically download and install the latest ButterCut version from GitHub while preserving libraries. Use when user wants to check for updates or update their installation for new features.

Add integration tests for type checker inference and checking functions

Guide for creating, auditing, and packaging Claude Code skills. This skill should be used when building new skills, improving existing skills, understanding skill structure, or packaging skills for distribution.

Step-by-step guide for adding support for a new AI editor format to PRPM - covers types, converters, schemas, CLI, webapp, and testing

CI Test Factory Droid Skill

Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration

Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.

Systematically review completed code implementations against original plans, requirements, and coding standards to ensure quality, plan alignment, and best practices adherence. Use this skill after completing any significant implementation work including features, refactorings, bug fixes, or architectural changes, when a numbered step or phase from a planning document has been finished, after implementing multiple related functions or components that form a logical unit, when finishing work that was specified in a technical specification or design document, after making substantial changes to existing code or architecture, before creating pull requests to validate implementation quality, when completing API endpoints, service layers, or data access implementations, after implementing test suites for new functionality, when refactoring code to ensure no behavior was inadvertently changed, after integrating with external systems or third-party services, when finishing user-facing features to verify requirements

Expert guidance for developing Claude Code hooks in TypeScript with shared utilities, esbuild compilation, and Vitest testing - distributes compiled JS while maintaining TypeScript development experience

Apply rigorous test-driven development methodology following the Red-Green-Refactor cycle (write failing test, implement minimal code to pass, refactor while staying green) that ensures tests genuinely verify behavior by requiring observed failure before implementation, preventing untested code and false-positive tests. Use this skill when implementing any new feature or functionality in any programming language, when fixing bugs or resolving defects in existing code, when refactoring code to improve design while preserving behavior, when adding new methods, functions, classes, or modules to a codebase, when modifying existing behavior or business logic, when writing code in any file that will be executed in production environments, when creating API endpoints, service methods, or controller actions, when implementing data validation, transformation, or processing logic, when building user interface components with testable behavior, when writing algorithms, calculations, or business rules, when integrating w

CI Test Claude Skill