테스트·보안 스킬

Plan and write Go tests using test-driven development, table-driven cases, subtests, mocks, and HTTP or database test patterns. The guidance also covers benchmarks, fuzzing, race detection, and coverage so you can check behavior and performance across a Go project.

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

• Starting a Go feature with a failing test
• Adding table-driven tests for edge cases
• Testing HTTP handlers or database code

Use this skill to write, update, and debug C++ tests with GoogleTest, GoogleMock, CMake, and CTest. It covers test structure, stable execution, coverage settings, and sanitizers, tools that help detect memory errors, undefined behavior, and data races.

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

• Writing or repairing C++ unit and integration tests
• Configuring GoogleTest discovery with CMake and CTest
• Diagnosing test failures or flaky behavior

Build a test suite for Django applications using pytest-django and the red-green-refactor workflow. This skill covers model, view, serializer, and Django REST Framework API tests, with factories for test data, mocks for external services, fixtures, and coverage reports.

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

• Writing tests for Django models and views
• Testing Django REST Framework endpoints
• Creating repeatable test data with factories

Use this skill to review security settings in Spring Boot services. It covers authentication and access control, input validation, SQL injection prevention, CSRF choices, secrets, security headers, rate limiting, dependency checks, logging, and file uploads, with a release checklist.

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

• Reviewing authentication and access rules
• Validating controller input
• Checking CSRF settings for an API

Review a Django project before a pull request or deployment with a structured verification checklist. It covers environment and configuration, migrations, code quality, tests and coverage, security scans, static assets, performance, and a final diff review, then organizes findings into a report.

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

• Checking a Django change before opening a pull request
• Reviewing migrations and test coverage before release
• Preparing a Django app for deployment

Run a structured verification pass after major code changes or before a pull request. Check build output, types, lint, tests and coverage, possible exposed secrets, and changed files, then summarize results and outstanding issues in a readiness report.

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

• Checking a change before opening a pull request
• Verifying a refactor across build, types, and tests
• Reviewing coverage and possible exposed secrets

Apply test-driven development to Spring Boot services: write failing tests first, implement the smallest change, then refactor while keeping tests green. Use JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo to cover unit, web, integration, and persistence behavior.

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

• Adding a Spring Boot feature or endpoint
• Fixing a bug with a regression test
• Refactoring while keeping tests green

Define expected behavior before changing a Claude Code project, then track capability checks and regression results as work progresses. The skill provides evaluation reports and pass@k reliability measures to show whether new behavior works and existing behavior remains intact.

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

• Set success criteria before implementing a feature
• Check whether existing behavior regressed after a change
• Summarize evaluation results before review

Use this skill to guide feature work, bug fixes, and refactoring with a test-first workflow. It helps define user journeys, add unit, integration, and end-to-end tests, implement code against them, and check for at least 80% coverage.

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

• Adding tests before implementing a new feature
• Planning coverage for a bug fix
• Testing API endpoints and user flows

Use this skill to audit Claude Code configuration with AgentShield. It checks project instructions, settings, MCP servers, hooks, and agent definitions for exposed secrets, risky permissions, command injection, and other configuration concerns, with reports and optional safe fixes.

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

• Auditing a new Claude Code project configuration
• Checking settings after changing MCP or hooks
• Reviewing configuration before committing changes

Plan and write Python tests with pytest, from test-driven development to reusable fixtures, mocks, parameterized cases, async tests, and coverage reports. It provides patterns for checking errors, side effects, APIs, and databases, and for organizing test suites that are readable and maintainable.

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

• Starting a Python feature with test-driven development
• Creating reusable test data and setup with fixtures
• Checking API errors or external calls with mocks

Create and maintain C++ tests with CMake, CTest, and GoogleTest or GoogleMock. Use the workflow to investigate failures and flaky tests, organize unit and integration coverage, and add coverage reporting or sanitizers, tools that detect memory and concurrency problems.

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

• Adding unit or integration tests to a C++ project
• Configuring GoogleTest and CTest with CMake
• Investigating a failing or flaky test

Review code that handles authentication, user input, secrets, API endpoints, payments, or sensitive data. The skill provides security checklists and implementation patterns covering validation, access control, injection, cross-site scripting, rate limits, logging, dependencies, and deployment readiness.

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

• Checking input validation and file upload handling
• Reviewing authentication and authorization code
• Preparing API endpoints for production deployment

Use this skill to check a Spring Boot project before a pull request, release, or deployment. It guides builds, static analysis, tests with coverage, security scans, and diff review, then organizes the results into a verification report.

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

• Checking a Spring Boot change before a pull request
• Reviewing test coverage and static analysis results
• Scanning dependencies for known vulnerabilities

Use this skill to guide feature work, bug fixes, and refactoring through test-driven development (TDD): write tests first, then implement and improve the code. It covers unit, integration, and end-to-end tests, with a target of at least 80% coverage.

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

• Starting a feature with tests
• Fixing a bug with test cases
• Refactoring while keeping tests green

Run a structured verification cycle for Spring Boot changes before a pull request or deployment. It covers builds, static code checks, tests with coverage reports, security scans, and a final diff review, then summarizes failures and readiness in a report.

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

• Verify a Spring Boot change before opening a pull request
• Check a project after a major refactor or dependency upgrade
• Review build, test coverage, and security scan results before deployment

Set success criteria before implementation, check new capabilities and regressions, and report agent reliability with pass@k measures. The framework supports code-based, model-based, and human review for Claude Code tasks.

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

• Define acceptance criteria before coding
• Check that changes do not break existing behavior
• Track agent success across repeated attempts

Work on tests for modern C++ projects with GoogleTest, GoogleMock, CMake, and CTest. Create or repair tests, diagnose flaky failures, and configure coverage or sanitizers, tools that help detect memory errors and data races.

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

• Writing or repairing C++ tests
• Setting up GoogleTest and CTest
• Investigating flaky test failures

Run a structured verification cycle for Django changes before a pull request or deployment. Check migrations, code style and types, tests with coverage reports, dependency and configuration security, performance, static assets, and deployment readiness in a reportable checklist.

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

• Checking Django changes before opening a pull request
• Verifying migrations after model or dependency changes
• Reviewing tests, coverage, and security before deployment

Design and write Python tests with pytest, using test-driven development (writing a failing test before implementation), reusable fixtures, mocks for external dependencies, parameterized cases, and coverage reports. It also covers async code and organizing unit and integration tests.

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

• Start a Python feature with a failing test
• Build reusable pytest fixtures
• Test errors and external calls with mocks

Use this skill to build and improve Go tests with a test-driven workflow. It covers table-driven tests, subtests, benchmarks, fuzzing, HTTP handlers, coverage checks, and practical ways to organize test helpers and dependencies.

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

• Adding table-driven tests for Go functions
• Checking HTTP handlers and error cases
• Benchmarking performance-critical code

Use this skill to audit Claude Code configuration with AgentShield. It scans files and settings such as CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions for security issues, misconfiguration, exposed secrets, and injection risks, with reports in several formats.

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

• Auditing a new Claude Code project
• Checking configuration changes before committing
• Reviewing MCP servers, hooks, and agent definitions

Use this skill to review application code around authentication, APIs, user input, secrets, payments, and sensitive data. It provides a security checklist and examples covering validation, access control, injection and browser attacks, rate limits, logging, dependencies, and security tests.

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

• Reviewing a new authentication flow
• Checking validation for user input or uploads
• Auditing API authorization and rate limits

Build and maintain Playwright end-to-end tests with examples for organizing test files, using Page Object Model, configuring browsers and CI runs, and saving reports, screenshots, traces, and videos. The guide also covers ways to identify and handle flaky tests.

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

• Structuring browser-based end-to-end tests
• Creating reusable page objects
• Running Playwright tests in CI