'qa' 검색 결과

Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

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

Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

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

Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"

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

Build QA quality dashboards, calculate defect metrics, analyze escape rates, and produce quality trend reports. Use this skill whenever a QA lead or manager needs to measure and communicate quality outcomes. Trigger on phrases like "quality metrics", "defect density", "escape rate", "bug trends", "quality dashboard", "sprint quality report", "test coverage metrics", "QA KPIs", "how is quality trending", "defect leakage", "production bugs this quarter", "mean time to detect", "quality scorecard", or any request to quantify, visualize, or report on the quality of a product or testing process. Also trigger when a manager asks "how is QA performing?" or an engineering lead asks "what does our defect data tell us?".

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

Read and control Aqara smart home devices: plugs, switches, lights, AC, locks, curtains, scenes. Trigger phrases: aqara, aqara hub, aqara lock, aqara curtain.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

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

Discord 테스트 봇으로 연결 정보와 읽기 권한을 확인하고, 메시지·파일·스레드 작업과 OpenClaw 응답을 증거로 검증하며 로그와 정리 결과도 확인합니다.

• 봇 식별 정보와 기록 읽기 권한 확인
• 메시지·파일·스레드 작업 검증
• OpenClaw 응답·순차 전송·입력 표시 검증

Fix iOS bugs by editing source code, rebuilding the app, deploying it again, and verifying the result on a real device. Preserve a state snapshot as test data to help detect recurrence.

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

• Fixing bugs reported by /ios-qa
• Verifying fixes after rebuilding and redeploying
• Preserving state snapshots for regression tests

Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.

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

• Check CLI commands and HTTP server health
• Observe lifecycle events associated with plugin hooks
• Check terminal startup and keyboard input

Test runnable software through normal and hostile end-to-end scenarios, checking complete behavior across a workflow. Investigate failures, apply fixes, rerun checks, and produce an evidence-backed report covering results, cleanup, and remaining risks.

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

• Check behavior with malformed input
• Verify cancellation and resumption
• Investigate flaky tests

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

Sets up QA testing processes: test strategies, Google Testing Standards test cases, P0-P4 bug tracking, quality metrics, progress reports, autonomous execution via master prompts, and OWASP security testing, with third-party QA handoff docs. Use when establishing QA infrastructure, writing test cases, executing test plans, or tracking bugs. Not for auditing an already-rendered UI (use frontend-visual-qa).

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

Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy check, pre-launch check, verify the deploy, test this page, does the page render, broken link, 404, image not loading. Also triggers proactively after a deploy or a new page launch where verification matters. Covers accessibility, performance, and SEO at the surface-signal level only: deep audits belong to `accessibility-audit`, `performance-optimization`, and `seo-technical`, and code-level debugging to `code-review-web`.

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

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality incident," "defect analysis," "improvement cycle." Not for: live release go/no-go decisions — use release-readiness. Not for ongoing metric dashboards — use qa-metrics. Not for reviewing existing test code quality — use ai-qa-review. Related: qa-metrics, test-reliability, test-strategy.

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

Perform QA testing on running web applications using cmux_browser. Covers functional testing, accessibility auditing, edge case testing, and structured reporting with evidence. **Triggers — use this skill when:** - User says "test this", "QA this", "QA this PR", "check the app" - User says "run QA", "verify the build", "test the UI" - User asks to "check if it works", "validate the feature" - User says "acceptance testing", "smoke test", "regression test" - User asks to "find bugs", "test for bugs", "break it" - User wants to "check accessibility", "run axe", "a11y audit" **Covers:** Any web application accessible via HTTP. Uses cmux_browser (Playwright under the hood) for all browser interactions.

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

Run automated QA checks on Grafema VS Code extension via Playwright + MCP cross-validation. Use when: (1) user says "/qa" to start or resume QA session, (2) user wants to validate extension panels against graph data, (3) user wants to re-check previously found bugs after a fix, (4) user wants to run a custom QA task. Requires Docker code-server running.

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

Manage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".

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

Spec-driven manual QA testing and Playwright E2E code generation. Orchestrates browser skills to navigate apps like a human tester, producing structured test reports or production-ready .spec.ts files. Always prompts user for credentials — never guesses or stores auth. Use for QA testing, E2E generation, login flow testing, or exploratory testing from a URL. NOT for AI-autonomous flows (see mk:agent-browser).

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

実装済みサイトのデザイン品質を体系的にチェックする。配置・余白・比率・レスポンシブなどデザイン的な問題を検出し、修正は行わず問題のリストアップに集中する。 Trigger: デザインQA, デザインチェック, レイアウト確認, デザイン検証, 表示崩れ確認, /design-e2e-qa

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

OpenClaw 전반의 품질을 지속적으로 검증합니다. 결함 재현부터 근본 원인 수정, 검토, 반영 확인까지 진행하고 실제 환경과 부하 검증 결과를 재개 가능한 보고서에 기록합니다.

• OpenClaw 여러 영역의 결함을 조사할 때
• 회귀 테스트와 독립 검토로 수정을 검증할 때
• 실제 연결, UI, 배포 패키지를 확인할 때

Launch GStack Browser, a visible Chromium browser controlled by an AI agent. Watch actions in a sidebar activity feed and use sidebar chat to request page navigation, clicks, form entry, and reading page content.

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

• Watching an AI agent operate a browser
• Requesting page navigation and form entry through sidebar chat
• Viewing browser actions during QA or design review