'qa' 검색 결과

OpenClaw의 QA Lab에서 Telegram 초안과 최종 메시지의 도착 순서를 검증합니다. QA Channel과 실제 Telegram 플러그인으로 같은 시나리오를 실행합니다.

• Telegram 초안과 최종 메시지 전달 확인
• QA Channel에서 전달 흐름 검증
• 실제 Telegram 플러그인으로 검증

Automate Booqable tasks through Rube MCP, a connection for agent tools. Discover supported actions, check the service connection, and execute with current input requirements, including workflows for bulk processing and collecting results across multiple pages.

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

• Find tools for a Booqable task
• Verify the Booqable connection
• Execute multiple Booqable operations together

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

Automate Booqable tasks through Rube MCP, a connection for agent tools. Discover supported actions, check the service connection, and execute with current input requirements, including workflows for bulk processing and collecting results across multiple pages.

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

• Find tools for a Booqable task
• Verify the Booqable connection
• Execute multiple Booqable operations together

Sequenced launcher that bootstraps QA on a project with no QA in place. Chains qa-project-context → test-strategy → test-planning in one guided run, then points you at automation. Use when: "set up QA on a new project," "QA from scratch," "no QA exists yet," "/qa-start." Not for: onboarding a QA engineer to an existing team with existing tests — use qa-project-bootstrap. Not for: "which skill do I use" with no clear match — use qa-do. Related: qa-project-context, test-strategy, test-planning, qa-project-bootstrap, qa-do.

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

OpenClaw의 기능 분류와 QA 근거를 대조하여 품질, 기능 충족도, 장기 지원 평가를 재검토하고 입력 데이터를 검증해 성숙도 점수표 문서를 갱신합니다.

• 기능 영역별 성숙도를 재검토합니다
• 예상 사용 절차의 충족도를 확인합니다
• QA 근거로 평가 문서를 갱신합니다

OpenClaw의 품질 검증 시나리오를 모의 환경이나 실제 서비스에서 실행하고, 실패 원인 수정과 보고서 확인, 여러 모델의 응답 스타일 비교를 지원합니다.

• 모의 환경이나 실제 서비스에서 품질 검증
• 실패 시나리오 원인 조사와 재검증
• 여러 모델의 캐릭터 표현 비교

Investigate failed Agent QA runs using recorded steps, logs, and saved evidence. Classify each failure, explain confidence and supporting findings, and identify the likely area to fix and the next action.

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

• Investigating a failed or interrupted Agent QA run
• Reviewing saved evidence and execution logs
• Comparing recurring failures across recent runs

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

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit," "first 30 days," "QA mentorship," "joining QA team." Not for: setting up QA on a brand-new project from scratch — use `qa-start`. Related: qa-start, qa-project-context, shift-left-testing, ai-qa-review.

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

Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.

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

• Verify adapter behavior after code changes
• Test task execution and team recovery
• Check that skills reach child tasks

Investigate failed Agent QA runs using logs, recorded artifacts, and local source code. Make a focused code or test-definition repair, then verify the affected behavior while keeping product and infrastructure defects visible.

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

• Repair a failed staging test from recorded evidence
• Update an outdated Agent QA YAML definition
• Distinguish test failures from product or infrastructure defects

Pre-publish QA framework for content. Brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, QA at scale via sampling, the QA workflow, and the discipline that distinguishes catch-problems QA from checkbox QA. Triggers on editorial QA, content review, pre-publish review, content audit, content QA process, AI-content audit, hallucination check, content sampling, programmatic QA, voice consistency check, brief adherence check. Also triggers when a content team is shipping sloppy work, when AI-co-authored content is reaching publish unaudited, when a QA process burns reviewers out, or when a programmatic SEO set needs sampling discipline. On a voice consistency check, this skill owns checking a draft against an existing voice system at the publish gate; use `brand-voice` when the voice system itself needs defining or documenting.

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

Create and fill .agents/qa-project-context.md with the project's tech stack, test frameworks, CI/CD pipeline, environments, quality goals, risk areas, team structure, and conventions. This is the one file every other QA skill reads first, so they skip redundant discovery and give context-aware advice. Use when: "set up QA context," "configure testing," "initialize project," first use of any QA skill. Not for: bootstrapping a brand-new project's QA end-to-end — use qa-start (which calls this skill as its first step). Related: qa-start, risk-based-testing, test-strategy, qa-metrics, playwright-automation.

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

Routing skill of last resort. Takes a plain-language QA situation and names the right 1-2 skills to use and in what order. Use ONLY when the request does not match any other skill's trigger phrases. Use when: "which skill should I use," "where do I start," "I'm not sure what to test," "/qa-do," or any vague QA situation that doesn't map to one skill. Not for: bootstrapping a brand-new project with no QA — use qa-start. Not for: capturing project setup/context — use qa-project-context. If the request clearly matches another skill, invoke that skill directly instead of routing through here. Related: qa-start, qa-project-context, test-strategy.

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

Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.

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

• Group QA findings by release
• Classify bugs by severity
• Apply labels to multiple issues and pull requests

[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.

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

Create and edit Agent QA tests, test suites, and hooks, then validate their structure and tool-generated IDs before running them. Use MCP, an agent tool connection, or the CLI within a configured workspace.

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

• Create and validate a checkout test for staging
• Update an existing test suite
• Check YAML definitions and IDs

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

[omh] Rendered UI needing a visual verdict: prepare observed-only rendered QA gates for web, frontend, image, document, and TUI surfaces. Use when the user says: visual-qa, visual qa, visual QA, visual quality assurance, visual check, web qa, web visual qa, screenshot qa.

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

Manual QA harness for the senpi coding agent itself. MUST USE after changing packages/ai, packages/agent, packages/coding-agent, or packages/tui — a green typecheck and `npm test` are NOT QA. Drives the real CLI from source in an isolated sandbox (never touches ~/.senpi or real credentials) across four channels: remote RPC (--mode rpc JSONL stdio), TUI smoke (node-pty on Windows, tmux on POSIX), mock loop (a local fake model server for deterministic, zero-token agent-loop runs), and CLI smoke (--help/--print/--list-models). Every helper ships a --self-test. Use whenever someone says qa senpi, test the agent, verify my change, rpc qa, tui qa, mock-loop qa, smoke the cli, or needs evidence that an agent-loop, tool, keybinding, or provider change works end to end. Capture evidence to local-ignore/qa-evidence/.

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

새 기능이나 제안을 PM, 설계, 개발, QA의 네 관점에서 동시에 검토합니다. 역할별 우려와 첫 행동을 정리하고 공통점과 의견 충돌을 요약합니다.

• 새 기능을 네 역할의 관점에서 검토
• 구현 전 제안의 우려 사항 확인
• 새로운 업무의 첫 행동 정리

Clean up an iOS app after /ios-qa by removing the DebugBridge package and its debug wiring. The cleanup covers StateServer, DebugOverlay, generated accessor code, and hooks added to the app.

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

• Cleaning up an iOS app after /ios-qa
• Removing the DebugBridge package
• Removing StateServer and DebugOverlay

Create acceptance criteria and a manual validation plan for feature changes. Cover successful flows, unusual inputs, failures, and performance limits, with observable outcomes and clear evidence requirements so reviewers can decide whether each criterion passes.

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

• Preparing a feature change for QA
• Reviewing a PR that changes user-visible behavior
• Planning regression checks after an incident