테스트·보안 스킬

Review regression coverage and test quality in Apache Pinot when behavior or tests change. Use it to assess whether code changes and bug fixes have relevant tests, including paths that handle different types or null values.

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

• Reviewing added or modified test files
• Checking production changes without test updates
• Checking regression tests for bug fixes

Investigate Pinot tests that fail intermittently in GitHub Actions. Use the skill to produce a report describing the evidence found and likely causes, helping explain failures that do not occur consistently.

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

• Investigating intermittent Pinot test failures
• Reporting evidence from GitHub Actions test failures
• Documenting likely causes of inconsistent test results

Run a named Pinot test class or individual method in the Maven module that contains it. Use it to focus test execution on a specific target within the project's module structure.

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

• Run a specific Pinot test class
• Run an individual test method
• Execute a test in its owning Maven module

Scans a chosen area of Kaku for hidden defects and usability problems using its fix history and alternative user paths. It separates evidence-backed findings from untested possibilities and reports affected paths, severity, and boundaries checked without issues.

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

• Scan a Kaku area before release
• Check related paths after a bug fix
• Inspect shell setup in a clean environment

Find gaps in how remove-ai-watermarks detects AI origin information and watermarks across new and retained datasets, then verify fixes and check that removable signals are cleared without breaking required image or stream properties.

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

• Audit newly collected data for unsupported signals
• Recheck retained data after detection changes
• Verify removal of newly detected watermarks

Check AI watermarks through Google, OpenAI, Microsoft, or Meta verification services. The skill links results to file hashes, identifiers used to verify file integrity, and records separate evidence for each configured account and verification route.

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

• Checking watermarks through provider verification services
• Comparing Gemini results across configured accounts
• Recording API and browser checks separately

Verify edited code with relevant build commands, type checks, automated code checks, and targeted tests. Finds commands in project configuration, fixes reported problems, and repeats the same checks until they pass.

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

• Checking affected code after source edits
• Finding validation commands in project configuration
• Fixing reported errors and rerunning the same checks

Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.

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

• Testing component rendering and form interactions
• Creating reusable test data with selective overrides
• Replacing modules and GraphQL hooks in tests

Generate a report with predictable output for acceptance tests of disposable executors, or temporary task runners. Retrieve agent settings, run the supplied report script with specified arguments, and publish the resulting file to S3.

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

• Generating a report for disposable executor acceptance tests
• Checking report output with specified arguments
• Publishing a verification report to S3

Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.

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

• Running daily full test suites
• Recording manual test results and evidence locally
• Preparing local test and Playwright maintenance candidates

Organize Nexent test assets into a traceable chain from requirements and bugs to cases, scripts, and results. Review existing coverage, maintain execution settings, and generate a registry and Excel views for formal testing.

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

• Designing test cases for new requirements
• Reviewing regression coverage after a bug fix
• Adding missing tests after development

Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.

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

• Add unit coverage for changed product behavior
• Write regression assertions for bug fixes
• Test error handling without external service calls

Review Apple platform app code for potential App Store rejection issues before submission. Check privacy, payments, safety, performance, and design using guideline references, risk categories, code examples, and a pre-submission checklist.

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

• Checking an app before App Store submission
• Reviewing payments and subscriptions
• Checking privacy and account deletion

Write and review unit and integration tests with Swift Testing. Check assertions, asynchronous behavior, and test structure, or convert existing XCTest tests using guidance on modern APIs and project conventions.

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

• Writing unit and integration tests
• Reviewing tests for asynchronous code
• Migrating existing XCTest tests

Write and configure unit tests, which check individual pieces of code, using Vitest. Replace dependencies with test substitutes, measure code coverage, compare saved outputs, and organize filtered or parallel test runs.

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

• Write unit tests for TypeScript code
• Replace functions and timers with test substitutes
• Measure coverage and compare saved outputs

Review an OpenSpec implementation against its specifications, tasks, and design decisions. The skill checks for missing work, uncovered scenarios, and inconsistencies, then produces a prioritized report with concrete recommendations and code references where available.

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

• Review an implementation before archiving
• Find incomplete tasks and missing requirement implementations
• Check whether scenarios have implementation and test coverage

Review interface code for accessibility, performance, theme support, responsive behavior, and problematic patterns. Receive a scored report with code locations, user impact, severity levels, and prioritized recommendations to guide subsequent fixes.

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

• Checking accessibility before release
• Reviewing performance issues in interface code
• Inspecting dark mode and mobile layouts

Scan code for security risks such as injection attacks and embedded secrets, then report findings by severity. Also check whether design documents record security decisions, trust boundaries, and accepted risks.

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

• Security checks before committing code
• Reviewing authentication and authorization changes
• Finding embedded keys and secrets

Routes security work to specialized guides for web and API testing, code review, threat intelligence, and incident response. Helps organize assessments from both attack and defense perspectives, including coordinated testing of detection capabilities.

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

• Planning a web or API security assessment
• Reviewing code for potential vulnerabilities
• Organizing detection rules and incident response

Test local web applications with Playwright, a browser automation tool. Write Python scripts to check interface behavior, inspect rendered pages, capture screenshots, and collect browser logs, with a helper that manages one or more application servers.

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

• Checking buttons, links, and form behavior
• Investigating interface issues with screenshots and logs
• Automating checks for local static HTML

Checks code changes before a pull request by reviewing builds, types, coding rules, tests, potential secrets, and changed files. Produces a report showing results, test coverage, and issues that need fixing.

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

• Checking changes before opening a pull request
• Verifying a completed feature
• Reviewing code after refactoring

Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.

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

• Accepting changes to a screenshot comparison baseline
• Committing the updated baseline version.json
• Running the baseline acceptance procedure with an explicit command

Review resolved dependency versions and relevant code for security vulnerabilities. Get findings with evidence, impact, and targeted remedies, distinguishing published dependency warnings from exploit paths demonstrated in the project.

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

• Check dependencies for known vulnerabilities
• Trace untrusted input to sensitive operations
• Locate potential secrets in committed files

Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.

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

• Auditing risks across a repository
• Checking state loss and resource limits in a TUI
• Checking dependencies for known vulnerabilities