테스트·보안 스킬

Run validation through Crabbox on Linux, macOS, Windows, or WSL2 using the configured provider. Track environment setup and results, including delegated Blacksmith Testbox runs, and report the actual provider and run ID.

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

• Run tests in the configured Crabbox environment
• Validate a change on Windows or WSL2
• Prove a user-facing bug fix with an end-to-end run

Set clear pass or fail criteria for Claude Code tasks before implementation, then track capability and regression evaluations as changes are made. The framework supports code, model, and human grading and records reliability measures such as pass@k.

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

• Defining success criteria before changing code
• Checking that new behavior works as expected
• Finding regressions after prompt or agent changes

Apply test-driven development when adding features, fixing bugs, or refactoring. The workflow starts with user journeys and failing tests, then implementation and refactoring, using unit, integration, and Playwright end-to-end tests with a target of at least 80% coverage.

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

• Writing tests before implementing a new feature
• Planning integration and end-to-end coverage for an API
• Refactoring code while keeping tests passing

Review application code for common security risks when adding authentication, handling user input or secrets, building API endpoints, or implementing payments. It provides practical checks for access control, injection, data exposure, dependencies, and related protections.

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

• Checking a new login or authorization flow
• Reviewing input handling and file uploads
• Auditing API endpoints before release

Guide feature work, bug fixes, and refactoring with test-driven development: write tests first, implement until they pass, then refactor. It covers unit, integration, and Playwright end-to-end tests, with an 80% coverage target.

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

• Start a feature by defining user journeys and tests
• Add tests before fixing a bug
• Plan unit, integration, and browser end-to-end coverage

Review code that handles authentication, user input, secrets, API endpoints, payments, or sensitive data. Checklists and implementation examples cover validation, access control, injection, cross-site scripting, request forgery, rate limits, sensitive logging, dependencies, and deployment preparation.

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

• Checking validation for user input and file uploads
• Reviewing authentication and role based access control
• Checking API security before a production release

Use this skill to structure Playwright end-to-end tests, configure browser projects and CI runs, and manage screenshots, videos, and traces. It also gives approaches for finding and reducing flaky tests, which pass inconsistently due to timing or race conditions.

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

• Structuring browser-based end-to-end tests
• Setting up Playwright projects and CI workflows
• Capturing screenshots, videos, and traces on failure

Review Django security practices for authentication, permissions, production settings, CSRF and XSS defenses, safe database queries, file uploads, API throttling, and security headers. It provides configuration and code examples for common application risks.

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

• Prepare Django settings for production deployment
• Review permissions and role based access
• Check queries for SQL injection risks

Use this skill after substantial code changes or before creating a pull request. It guides a staged review of build, types, lint, tests, security checks, and diffs, then produces a report showing results and issues to fix.

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

• Verifying a feature after implementation
• Checking quality gates before creating a pull request
• Reviewing a refactor across build, tests, and code changes

Check application code for common security risks while adding authentication, processing user input or secrets, creating API endpoints, or building payment features. Its checklist covers validation, access control, injection, cross-site attacks, data exposure, rate limits, and deployment readiness.

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

• Reviewing authentication and role checks
• Checking file upload validation
• Auditing API security before deployment

Use AgentShield to inspect Claude Code configuration for exposed secrets, overly broad permissions, unsafe MCP servers, hook command injection, and prompt injection risks. The skill explains scan options, report formats, safe automatic fixes, and CI integration.

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

• Scanning a new Claude Code project configuration
• Checking configuration changes before committing
• Generating JSON, Markdown, or HTML security reports

Use this framework to define expected behavior before a Claude Code implementation, test capabilities and regressions, and report outcomes. It outlines code, model, and human graders, along with pass@k and pass^k measures for agent reliability.

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

• Setting acceptance criteria before implementation
• Testing new agent capabilities and regressions
• Measuring success across repeated attempts

Follow a test-driven workflow for new features, bug fixes, and refactoring: write tests first, implement only what makes them pass, then refactor and review coverage. It covers unit, integration, and Playwright end-to-end tests, with an 80% coverage target and examples for isolating external services.

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

• Writing tests before implementing a new feature
• Adding API or component tests for a code change
• Checking edge cases and coverage during refactoring

Run a structured verification cycle for Spring Boot projects before pull requests, major changes, or deployment. It covers builds, static analysis, tests and coverage, security scans, and a final diff review, with a report of readiness and issues to fix.

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

• Check a Spring Boot change before opening a PR
• Verify a service after a major refactor or dependency upgrade
• Review tests and coverage before deployment

Use this skill to review security controls in Java Spring Boot services. It covers authentication and authorization, input validation, SQL injection prevention, CSRF, secret management, security headers, CORS, rate limiting, dependency checks, and sensitive logging.

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

• Adding JWT or session authentication
• Protecting endpoints with authorization rules
• Validating input and preventing SQL injection

Check a Django project before a pull request or deployment. The workflow covers code quality, database migrations, tests and coverage, security, configuration, static assets, and a final diff review, with findings collected in a verification report.

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

• Preparing a Django pull request
• Checking model changes and migrations
• Reviewing test coverage and security

Use this skill to develop Spring Boot services through test-driven development. It guides you in writing unit, web, integration, and persistence tests with JUnit 5, Mockito, MockMvc, and Testcontainers, then checking coverage with JaCoCo.

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

• Adding a Spring Boot feature or endpoint
• Fixing a bug with a regression test
• Testing database access or security rules

Build and maintain Playwright end-to-end tests with examples for page objects, test organization, browser and mobile projects, CI integration, and failure artifacts such as screenshots, videos, and traces. Includes approaches for finding and handling flaky tests.

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

• Organizing browser-based end-to-end tests
• Setting up Playwright projects and config
• Saving reports and failure screenshots

Use idiomatic Go testing patterns with a test-driven workflow, table-driven tests, subtests, mocks, and HTTP or database checks. The examples also cover benchmarks, fuzzing, race detection, and coverage to help assess correctness and performance.

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

• Starting a Go feature with a failing test
• Organizing edge cases as table-driven tests
• Checking HTTP handlers or database behavior

Build a Django test suite with a test-driven development workflow. The skill covers pytest-django setup, reusable test data with factory_boy, model and view checks, Django REST Framework API tests, mocking external services, integration tests, and coverage reports.

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

• Starting a test suite for a Django project
• Testing models, views, and serializers
• Checking Django REST Framework endpoints

Build and organize Python tests with pytest, from the red-green-refactor TDD cycle to reusable fixtures, mocks, parametrized cases, and async checks. The skill also covers test selection, temporary files, exception testing, and measuring coverage so teams can assess important code paths.

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

• Starting tests for new Python behavior with TDD
• Organizing shared fixtures for a test suite
• Testing code that calls external services

Apply Go testing practices with a test-first workflow. The guide covers table-driven and subtests, benchmarks, fuzz testing for varied inputs, HTTP handler checks, mocks, and coverage so tests can check behavior and performance.

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

• Writing tests before implementing a Go function
• Testing multiple input and error cases
• Benchmarking performance and allocations

Structure evaluations for Claude Code tasks by defining success criteria before implementation, checking new capabilities and regressions, and recording results. It describes code-based, model-based, and human graders, plus pass@k and pass^k reliability measures.

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

• Defining success criteria before a coding task
• Checking whether changes cause regressions
• Tracking agent reliability across attempts

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