테스트·보안 스킬

Review plans involving customer data, compliance, or production access. Examine threats, potential damage, detection, incident response, notification requirements, and vendors, then summarize whether the plan can proceed, needs mitigation, or should be blocked.

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

• Reviewing a feature that handles customer data
• Preparing for a SOC 2 or ISO 27001 audit
• Assessing a vendor that will access data

Assess security risks in AI systems by scanning prompts for known attack patterns and scoring data exposure, poisoning, and tool abuse risks. Map findings to MITRE ATLAS, an AI threat framework, and identify protective controls.

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

• Scan application prompts for injection and jailbreak patterns
• Review malicious instructions in retrieved documents
• Assess training data exposure and poisoning risks

Prepare for ISO 27001 audits by reviewing six areas of an information security management system: audit coverage, risks, access, suppliers, incidents, and management reviews. Summarize evidence gaps, readiness, and three priority actions with owners and timelines.

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

• Prepare evidence for an annual internal audit
• Check readiness before certification or surveillance audits
• Review audit scope after business or system changes

Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.

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

• Justify security budgets with estimated financial losses
• Plan SOC 2 or ISO 27001 compliance work
• Prepare incident coordination and communication plans

Choose checks for cmux changes, add tests that reproduce observable bugs, and verify that Swift test files are included in build targets. It also guides local and CI validation, including evidence that selected tests actually ran.

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

• Choose validation checks for a cmux change
• Add a regression test that reproduces a bug
• Verify Swift test files are included in the build

Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.

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

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

Analyze a codebase to identify valuable assets, attack entry points, and realistic abuse paths. Produce a concise Markdown threat model that explains risk priorities, distinguishes existing protections from proposed mitigations, and makes assumptions explicit.

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

• Map attack entry points in a codebase
• Assess threats within a specific project directory
• Prioritize risks to sensitive data and credentials

Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

Debug local web and Electron apps through a persistent Playwright session in js_repl, an interactive JavaScript environment. Reuse browser connections while checking user interactions, visual states, screen sizes, and screenshots after changes.

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

• Rechecking an interface after code changes
• Testing buttons and complete user flows
• Inspecting layouts at desktop and mobile widths

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Assess FastMCP vulnerability reports by preserving evidence, reproducing claims, and identifying which component owns the failed protection. Establish affected versions and realistic impact, review proposed fixes, and recommend how the report should be handled.

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

• Assessing vulnerability reports and bug bounty submissions
• Separating OAuth proxy issues from deployment problems
• Checking affected versions and realistic impact

Write regression tests that catch recurring bugs in FastMCP changes using pytest. Covers reproducing failures before a fix, testing requests without a network server, and checking outgoing requests while replacing external services with test substitutes.

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

• Reproducing a bug before testing its fix
• Testing MCP behavior without a network server
• Checking requests sent to external services

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

Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.

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

• Add screenshot coverage for chat or settings screens
• Check layouts at 420px and 200px widths
• Show permission requests using mock data

Analyze repeated CI test runs to find tests that pass and fail without code changes. Summarize failure rates, investigate likely causes, and recommend fixes, monitoring, or temporary exclusion based on the available evidence.

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

• Investigating intermittent CI test failures
• Comparing failure rates across repeated test runs
• Reviewing tests already marked for temporary exclusion

Prepare a long play session with timed observation checkpoints and logs for memory growth, stability, and player fatigue. It creates the testing protocol and analysis template; a human plays the game and records the findings.

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

• Prepare an endurance test before release
• Check for recurring memory issues after a fix
• Track crashes and performance over a long session

Check a game build before handing it to QA, the team responsible for quality checks. Run automated tests, review coverage gaps, confirm critical paths with the developer, and produce a report with results and unresolved checks.

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

• Checking a build before QA hand-off
• Rechecking a build after fixing a failure
• Reviewing platform-specific controls and behavior

Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.

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

• Create a base library of test helpers
• Share repeated test setup and result checks
• Generate object factories for a specific game system

Set up automated testing before implementation begins. Detect the configured game engine, create test folders and runner configuration, and prepare a GitHub Actions workflow so tests can run automatically on each push.

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

• Set up automated testing before the first sprint
• Create test folders and runner configuration
• Prepare GitHub Actions to run tests on each push

Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.

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

• Planning QA for a sprint or game feature
• Preparing manual test cases from acceptance criteria
• Recording test results, bugs, and screenshot evidence

Review test files and manual verification records for development tasks. Check whether expected behavior, edge cases, screenshots, and required approvals are covered, then report evidence gaps and distinguish completion blockers from advisory improvements.

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

• Reviewing test evidence for a single development task
• Auditing evidence across a sprint or system
• Checking screenshots and required visual approvals

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

Create a game development test plan for a sprint, feature, or individual task. Classify the work and specify automated tests, manual checks, basic functionality checks, and playtest needs from documented requirements.

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

• Plan testing before a sprint starts
• Separate automated tests from manual checks
• Define basic checks before a QA handoff

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