테스트·보안 스킬

Plan JavaScript and TypeScript tests across unit, integration, and end-to-end levels. Get guidance for Jest, Vitest, and Testing Library, along with mocking, fixtures, test infrastructure, and test-driven or behavior-driven workflows.

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

• Set up a testing environment for a new project
• Write unit tests for functions or classes
• Test APIs, services, and frontend components

Use this skill to examine RAM captures with Volatility, a memory analysis framework. It guides acquisition, process and network inspection, and artifact extraction for incident response or malware investigations, with workflows for Windows, Linux, and macOS dumps.

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

• Investigating suspicious processes in a memory dump
• Extracting network and file artifacts from RAM
• Analyzing malware from a captured system image

Support defensive malware triage and incident response by identifying samples, guiding static and dynamic analysis, examining behavior, and extracting indicators of compromise (IOCs). The skill helps document findings and suggest detection or mitigation steps for authorized security work.

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

• Triaging a suspicious file during incident response
• Extracting network and host indicators from a sample
• Guiding sandbox and behavioral analysis

Review React, Vue, Angular, and browser JavaScript for cross-site scripting (XSS) risks. Identify unsafe HTML rendering, URL handling, and event patterns, then organize findings by severity with practical fixes, secure coding examples, and a prevention checklist.

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

• Checking frontend code for unsafe HTML rendering
• Reviewing user input and URL handling for XSS risks
• Getting severity-ranked findings and suggested fixes

Use this skill to plan authorized firmware security reviews for embedded devices. It covers ways to acquire and extract firmware, inspect filesystems and binaries, identify common security weaknesses, emulate software, and document findings with remediation guidance.

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

• Planning an authorized router firmware review
• Extracting and exploring an IoT firmware image
• Checking embedded files for credentials or weak settings

Implement and review client-side security measures in frontend code. Address cross-site scripting (XSS) with safe DOM handling and sanitization, and guide input validation, Content Security Policy, secure redirects, authentication storage, and browser security features.

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

• Preventing XSS when displaying user-generated content
• Configuring a Content Security Policy for a frontend
• Reviewing form validation and URL handling

Create end-to-end tests for important user journeys with Playwright or Cypress. Get guidance on stable selectors, test data, retries, tracing, and isolated runs, plus ways to run tests in CI and capture artifacts.

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

• Automating critical user journeys
• Debugging flaky end-to-end tests
• Setting E2E testing standards

Plan GDPR-aligned data handling for systems that process personal data in the EU. Get practical guidance on consent management, data subject requests, privacy controls, and privacy-first architecture, including implementation patterns from the accompanying playbook when needed.

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

• Designing consent management for an application
• Handling requests from people whose data is stored
• Reviewing privacy controls for an EU data system

Use this skill to coordinate code reviewers with different specialties, such as security, architecture, performance, and code quality. It combines their findings, identifies conflicting recommendations, and produces a unified report with prioritized issues and improvement suggestions.

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

• Reviewing a project across security and code quality
• Getting architecture and performance feedback together
• Combining findings from independent reviewers

Review direct and transitive project dependencies for known vulnerabilities, license concerns, outdated packages, and supply chain risks. Get prioritized findings, upgrade options with compatibility notes, and practical remediation steps for a security report or maintenance plan.

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

• Scanning dependencies for known vulnerabilities
• Reviewing package licenses for compliance concerns
• Finding outdated packages and upgrade paths

Use this skill to assess a code change or codebase across quality, architecture, security, performance, testing, and documentation. It organizes findings by priority and provides remediation guidance, with optional focus areas such as security, performance, or framework practices.

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

• Reviewing a change across several quality areas
• Finding security and performance risks
• Checking tests and documentation for gaps

Audit web or mobile experiences against WCAG accessibility criteria. The skill combines automated scans with manual checks such as keyboard use, screen readers, focus order, and contrast, then maps barriers to user impact and gives remediation steps and retesting guidance.

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

• Auditing a website against a chosen WCAG level
• Finding keyboard and screen reader barriers
• Prioritizing accessibility fixes by user impact

Map an attacker’s goal into branches of possible attack paths, then annotate the paths with factors such as cost, skill, time, and detectability. Use the resulting tree to spot defense gaps, prioritize mitigations, and explain security risks.

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

• Mapping possible attack paths
• Finding gaps in security controls
• Prioritizing defensive investments

Implement and review secure backend code, with guidance on validating inputs, protecting authentication and APIs, and preventing common vulnerabilities. It can also help secure database access, error handling, external requests, and security logging.

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

• Adding input validation to an API
• Reviewing backend code for injection risks
• Implementing secure authentication

Write unit tests for shell scripts with Bats, the Bash Automated Testing System. The skill covers test structure, helpers, fixtures, setup and teardown, and checks for exit codes, output, and side effects, including running the tests in CI pipelines.

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

• Testing shell script exit codes and output
• Adding fixtures and setup or teardown
• Using test-driven development for scripts

Support authorized analysis of protected software by identifying obfuscation and anti-debugging techniques. The skill helps document findings and suggest defensive measures for malware analysis, security research, approved testing, and training exercises.

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

• Analyzing malware within an approved scope
• Studying anti-debugging in a CTF
• Reviewing software protections for security research

Designs realistic mock APIs for frontend and integration development, tests, and demos. It helps define routes, response and error formats, authentication flows, latency, and state changes, with deterministic fixtures and guidance for running and switching scenarios.

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

• Mocking a third-party API during development
• Unblocking frontend work before the backend is ready
• Preparing realistic API responses for a demo

Review a project’s direct and transitive dependencies for known vulnerabilities, licensing concerns, supply-chain risks, and outdated packages. Get prioritized findings, upgrade options with compatibility notes, and practical remediation steps for a security report or follow-up plan.

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

• Check dependencies for known vulnerabilities
• Review package licenses and compliance risks
• Find outdated packages and upgrade paths

Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.

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

• Verify buttons, links, and form behavior
• Investigate problems in dynamic web interfaces
• Capture screenshots of local applications

Use test-driven development for features, bug fixes, refactoring, and behavior changes. Write a focused test first, confirm it fails for the expected reason, then implement the smallest change that passes and refactor while keeping tests green.

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

• Starting a feature with a clear behavior test
• Reproducing a bug before fixing it
• Refactoring while checking for regressions

Choose and interpret coverage analyses for an existing test suite, including code structure, mutation testing, requirements traceability, and API integration. The reference explains what each signal measures, its blind spots, suitable uses, and cost considerations; coverage is not treated as proof of test quality.

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

• Choosing a coverage measure for an existing suite
• Interpreting branch or mutation coverage results
• Checking test links to requirements or API surfaces

Add new test files for critical business logic changed locally. By default, inspect uncommitted and untracked changes, or the latest commit when the working tree is clean. The workflow analyzes coverage needs and verifies tests without changing existing test files.

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

• Adding tests for new or changed logic
• Finding gaps in coverage for local changes
• Covering the latest commit after changes are committed

Test rule-enforcing skills with a RED-GREEN-REFACTOR cycle adapted from software testing. Run pressured scenarios without the skill, capture failures and rationalizations, then revise and retest the documentation to close loopholes.

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

• Test a new TDD or compliance skill before release
• Find ways an agent may bypass a skill's rules
• Improve skill instructions after pressure tests

Use this skill after business logic changes, refactoring, or dependency updates to identify failing tests and coordinate repairs. It aims to keep tests aligned with the current implementation while preserving their original purpose and checking the full suite again.

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

• Fix tests after a refactor
• Update outdated test expectations
• Repair test setup or mocks