테스트·보안 스킬

Review unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.

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

• Prioritizing open bugs at the start of a sprint
• Organizing new bugs after a team QA review
• Reviewing a backlog with more than ten open bugs

Create a game release checklist tailored to target devices and distribution requirements. Review builds, bugs, store information, and launch preparations, then report readiness while clearly separating known blockers from checks that could not be assessed.

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

• Check game readiness before release
• Review requirements for a chosen storefront
• Identify release blockers and missing evidence

Audit game code for save tampering, cheating, network weaknesses, input validation gaps, exposed data, and dependency risks. Produce a report with severity ratings, repair priorities, release recommendations, and explicit notes about areas that could not be assessed.

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

• Auditing game security before a public release
• Checking risks before enabling online or multiplayer features
• Reviewing save loading and external input handling

Review game data and formulas for combat, economy, progression, or loot. Compare values with documented targets, identify dominant strategies and broken resource loops, and produce prioritized adjustment recommendations while clearly marking areas that lack enough data.

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

• Comparing weapon damage and combat effectiveness
• Finding resource loops and pricing problems
• Reviewing experience and power progression

Create a game playtest report template or turn session notes into organized feedback. Separate gameplay problems from bugs, compare observations with design intent, and identify priorities for design changes, balance adjustments, and polish.

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

• Preparing a playtest report template
• Organizing raw playtest notes
• Separating gameplay issues from bugs

Review skill and agent definitions for structural issues and whether their instructions meet expected behavior. Four modes cover structure, test specifications, category criteria, and coverage reports that reveal missing specifications or checks.

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

• Check one skill or all skills for structural issues
• Compare skill or agent instructions with a test specification
• Review definitions against category criteria

Compare documented permissions and data boundaries with actual code to find meaningful gaps. Produce findings that connect each documented rule to implementation evidence, identify who could exploit it and who is affected, and propose a concrete fix.

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

• Auditing code built by AI agents
• Checking access controls against documented permissions
• Finding gaps between documentation and code

Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.

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

• Writing test cases from user stories
• Preparing acceptance test scenarios
• Checking invalid inputs and boundary cases

Test the pages affected by a branch or pull request in a browser. The skill checks rendered pages and key interactions, then reports passes, failures, skipped checks with reasons, and steps to reproduce problems.

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

• Checking pages affected by a pull request
• Testing key interactions after a branch change
• Recording failures and reproduction steps

Build and exercise an iOS app in a simulator using XcodeBuildMCP. Collect screenshots, logs, and human verification results, then report which checks passed, failed, or were skipped, alongside the overall outcome and remaining failures.

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

• Checking iOS changes before handoff
• Keeping screenshots and logs as test evidence
• Tracking results for each screen or test area

Test user journeys affected by a branch’s changes in a real browser. Check correctness and the experience for intended users, fix small defects with regression tests, and commit fixes alongside a report documenting results and unresolved decisions.

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

• Check user-facing changes before a PR is merged
• Test complete user journeys affected by a branch
• Fix small defects and add regression tests

List and capture every interface state added or changed by a pull request, a proposed code change. Include error states, toggles, buttons, forms, and edited pages so reviewers can inspect their appearance.

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

• Capture interface states changed by a pull request
• Review screenshots of error states
• Inspect toggles, buttons, and forms

Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.

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

• Checking the value of a new or changed Vitest test
• Finding overlapping tests that can be consolidated
• Reviewing tests that break during behavior-preserving refactoring

Verify a local OpenSEO MCP server, which exposes tools to AI agents, through real DataForSEO calls and a headless Claude trial. Check protocol correctness alongside tool discovery, input rules, response size, errors, and asynchronous task recovery.

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

• Checking an MCP tool after adding or changing it
• Testing whether an agent can choose tools from their descriptions
• Verifying queued tasks and recovery using taskId

Evaluate changes to OpenSEO skills by running fresh Codex sessions against a local backend. Compare saved reports using weighted criteria, then inspect tool logs to understand failures and check whether revised instructions improve output.

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

• Comparing report quality before and after skill edits
• Checking revised instructions across different websites
• Scoring SEO audit reports against defined criteria

Automate real browser tasks to test websites, complete forms, and collect page information. The skill guides agents through identifying clickable elements, interacting with pages, comparing page states, and saving screenshots or PDFs.

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

• Testing form submissions and page navigation
• Comparing page appearance before and after changes
• Extracting page text and saving PDFs

Create and run tests for interactive command-line tools and terminal interfaces using @microsoft/tui-test. Simulate keyboard input, check visible text, and compare screen snapshots in a separate terminal environment for each test.

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

• Testing selection prompts with arrow keys and Enter
• Checking terminal screen snapshots
• Automating text entry and keyboard navigation

Verify OpenWork changes by running the real product and following user or client actions. Choose suitable tests, capture screenshots and reports, and demonstrate that the check fails on dev but passes on the changed branch.

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

• Verifying real product behavior before opening a PR
• Preparing screenshots and test evidence for a reviewer
• Checking a fix against dev and the changed branch

Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.

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

• Screening an outside contributor’s pull request before execution
• Checking encoded code and unexplained network calls
• Reviewing dependency changes and installation scripts

Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.

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

• Investigating unexplained errors in shipped OpenWork builds
• Identifying the PR that introduced a failure
• Reproducing errors on the affected runtime

Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.

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

• Check error messages and retry progress
• Inspect text retained after an interrupted reply
• Review grouped parallel tool calls

Review changed test specifications for cases where broken behavior could still pass. Report concrete gaps supported by the changes and implementation, with a minimal fix and an observable condition for resolving each advisory finding.

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

• Reviewing whether changed tests prove their stated behavior
• Finding UI tests that bypass the interaction being tested
• Checking whether save tests observe newly saved data

Write tests that demonstrate a pull request’s user-visible changes through before-and-after steps, screenshots, and recorded observations. Extend an existing core journey or create a one-off proof that helps reviewers understand the outcome and access boundaries.

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

• Demonstrating a feature’s before-and-after behavior
• Adding a missing step to an existing core journey
• Proving permission boundaries for different users

Review code changes for newly introduced security issues with a plausible attack path. Produce findings for the Warden security summary, including affected lines, severity, a minimal fix, and observable conditions for confirming the issue is resolved.

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

• Checking a PR for newly introduced vulnerabilities
• Reviewing CI changes that expose secrets or write access
• Inspecting Electron changes for unsafe permissions