테스트·보안 스킬

Checks content or code before publication or deployment through two independent agent reviews using the same criteria. Requires both to pass, repeats review after fixes, and hands unresolved issues to a human when the iteration limit is reached.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking factual claims before publishing content
• Reviewing customer-facing copy against brand rules
• Adding independent review before production deployment

Implement and review security measures in Quarkus applications. Covers sign-in, access permissions, input validation, password hashing, secret storage, request limits, audit logs, and checks for known vulnerabilities in dependencies, with implementation and configuration examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding JWT or OIDC authentication to a Quarkus API
• Checking role permissions and resource ownership
• Reviewing input validation and database queries

Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding behavior tests to React forms and components
• Testing custom hooks and asynchronous updates
• Simulating successful and failed API responses

Assess whether an application is ready for production using local files and authorized evidence. Reviews authentication, data, payments, and operations, then reports release blockers, prioritized fixes, and a readiness score without uploading repository contents to an external audit service.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking application readiness before launch
• Reviewing release risks after a merge
• Finding production risks beyond passing CI checks

Review Perl code that handles user input, files, external commands, databases, and web output. Use concrete examples and a security checklist to identify unsafe patterns and apply input validation, parameterized queries, and appropriate output encoding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing user input validation in Perl
• Checking file access and external command execution
• Preventing SQL injection in DBI queries

Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing Perl tests before implementation
• Migrating tests from Test::More to Test2::V0
• Testing API and database interactions in isolation

Verify Quarkus services before pull requests or deployment through builds, code analysis, tests, coverage reports, and security scans. The workflow also checks native executables, containers, performance, health endpoints, configuration, and documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a Quarkus service before a pull request
• Verifying refactoring or dependency upgrades
• Checking native executable compatibility

Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding REST endpoints with tests first
• Reproducing bugs before fixing them
• Testing Apache Camel routes and event handling

Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building Laravel features test first
• Testing API authentication and permissions
• Simulating payments, mail, and queues in tests

Review safeguards for AI agents authorized to sign or send transactions. Cover malicious instructions hidden in external data, spending caps, pre-send simulation, automatic stop conditions, protected transaction routing, and private-key handling through layered security checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Audit a trading bot with transaction authority
• Set per-transaction and daily spending limits
• Design pre-send checks and automatic stops

Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding tests to existing Kotlin code
• Developing new functions by writing tests first
• Testing coroutines and Flow behavior

Review Laravel authentication, permissions, database operations, forms, APIs, and production settings for security weaknesses. Use implementation examples to address unsafe input handling, exposed secrets, session risks, and insufficient access controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing login and permission controls
• Checking database queries and input validation
• Reviewing forms for forged requests and unsafe scripts

Check a Laravel project before merging or deploying. Work through environment settings, code checks, tests and coverage, dependency security, database changes, caches, queues, and scheduled tasks, stopping when a required check fails.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a Laravel project before opening a pull request
• Verifying a major refactor or dependency upgrade
• Checking readiness for staging or production deployment

Review US healthcare software for HIPAA privacy and security concerns. The skill guides checks on protected health information, vendor agreements, minimum necessary access, and audit records, while directing implementation and specialized review to related skills.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing AI-generated visit summaries for HIPAA concerns
• Checking patient data flows into analytics services
• Planning minimum necessary access and audit records

Review healthcare applications for exposure of patient and staff information. Classify sensitive data, design access restrictions for individual database rows, record data access and changes, and check common leaks through logs, URLs, and browser storage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code that handles patient records
• Design access restrictions between healthcare facilities
• Record access to and changes in sensitive data

Helps build Go tests using a test-first workflow. Covers grouped test cases, HTTP response checks, performance benchmarks, fuzzing to explore generated inputs, and coverage reports showing which code was exercised by tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing Go functions with tests written first
• Adding normal and error cases to existing tests
• Measuring execution time and memory allocations

Set up deployment checks for healthcare applications covering clinical decision support, patient information exposure, data integrity, workflows, and integrations. Block releases when critical tests fail, and flag lower workflow or integration pass rates for review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking an electronic health record application before deployment
• Testing changes to drug interactions or dose validation
• Checking patient data exposure after access control changes

Write and organize F# unit and integration tests with xUnit, FsUnit, and Unquote. Use FsCheck to generate test inputs and check general rules, replace dependencies for isolated tests, and review test quality and coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing unit tests for F# code
• Checking general rules with generated inputs
• Testing ASP.NET Core API integration

Create rules that detect command patterns, file edits, prompts, or completion events and issue warnings or block matching actions. Configure checks for dangerous commands, sensitive files, and debug code using text patterns or multiple conditions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Blocking dangerous commands
• Warning about edits to sensitive files
• Detecting debug code during file edits

Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing Django features by writing tests first
• Testing API authentication and input validation
• Generating reusable test data

Build Playwright tests that reproduce browser interactions, organize reusable page operations, and run checks automatically. Investigate tests that fail inconsistently, and save screenshots, videos, and execution traces to help diagnose failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing login and search flows
• Organizing reusable page operations
• Investigating intermittent test failures

Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a Django pull request
• Reviewing database migrations
• Checking test coverage targets

Check learning-log timestamps, free disk space, and shortcut-related phrases before Claude Code ends a session. A Stop hook, which runs when the agent tries to finish, warns or blocks completion according to configured rules without using AI judgment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking learning records after complex editing tasks
• Blocking completion when disk space is critically low
• Flagging phrases that suggest skipped checks

Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing C++ unit and integration tests
• Configuring GoogleTest and CTest
• Investigating tests that fail inconsistently