'qa' 검색 결과

브라우저, API, 명령줄 도구와 백그라운드 처리의 오류를 조사하고 수정·검증합니다. 세 단계의 점검 범위를 선택하고 수정 근거와 출시 판단 자료를 받습니다.

• 웹사이트 오류 수정
• API와 CLI 동작 확인
• 작업과 webhook 처리 확인

Create a draft pull request for reviewing Storybook changes. Prepare a title, required labels, and a description using the repository template, including verified manual testing steps that another maintainer can follow.

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

• Submit Storybook changes for review
• Choose category, CI, and manual QA labels
• Prepare reproducible manual testing instructions

Connect work from multiple AI agents to GitHub Projects. Synchronize task cards and statuses, assign work based on expertise and workload, and generate progress reports so teams can track assignments, priorities, and blockers on shared boards.

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

• Synchronize agent tasks with GitHub Projects cards
• Assign work based on expertise and workload
• Track sprint progress and blocked tasks

Check the appearance and interaction states of web pages, terminal interfaces, and paginated documents. Uses captured images, light and dark themes, viewport comparisons, and independent reviews to produce evidence-backed verdicts for each checklist item.

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

• Checking a UI after implementation changes
• Comparing a page with a design reference
• Finding Japanese text clipping and awkward wrapping

Breaks long-running goals into small, verifiable steps, tracks progress, and records evidence from actual operation. Checkpoints preserve what has been proven so work can resume after interruptions and continue toward explicit completion criteria.

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

• Managing a long-running development goal
• Resuming work after an interruption
• Recording evidence for completion criteria

Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.

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

• Adding automated tests to an existing feature
• Testing complete usage flows with E2E tests
• Adding API tests using the existing test setup

Set up Antigravity 2.0 Agent Manager alongside Antigravity IDE to coordinate parallel development agents. Assign roles and folder boundaries, review their changes in the editor, and use Git checkpoints to manage shared work.

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

• Setting up Agent Manager alongside the IDE
• Assigning frontend, backend, and QA roles
• Separating editing scopes to avoid conflicts

Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.

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

• Run automated checks on the actual release branch
• Check whether a PR merges into the release branch
• Manually test terminal responsiveness and input behavior

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

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

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Find relevant QwenPaw documentation and source files for questions about setup, configuration, skills, memory, and other features. It maps question keywords to likely file paths so the agent can read and verify the right material.

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

• Find documentation for installation or configuration questions
• Locate source files related to skills or memory
• Identify where to investigate errors or CLI behavior

Find the QwenPaw documentation and source files most relevant to a question. This skill maps topics such as installation, configuration, skills, and memory to likely reading paths, helping an agent focus its investigation.

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

• Finding installation and configuration references
• Locating documentation for skills and MCP
• Tracing memory and multi-agent behavior

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

Create or update a sprint plan, a short development work plan, using existing work items, completed work, and available capacity. Organize priorities, carryover, dependencies, and risks, and produce a progress report.

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

• Plan the next sprint around available capacity
• Re-estimate unfinished work carried into the next sprint
• Update task priorities and estimates

Create an onboarding document for a new contributor or agent, tailored to their role. Gather project context, relevant conventions, key files, current work, and suggested first tasks into a practical starting guide.

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

• Preparing a guide for a new programmer
• Orienting designers or narrative contributors
• Sharing current work with QA or production staff

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

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

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Test CodexBar against real provider services, check application settings, and verify menu contents. Use command-line checks and visual evidence to distinguish authentication problems, API mismatches, and display issues before a release.

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

• Checking provider connections before a release
• Investigating missing usage data or authentication failures
• Comparing menu contents with enabled providers

Prepare Handsontable changes for review by checking branch names, running required checks, and creating or updating draft pull requests. Fill the project template with test evidence and add changelog entries in the required order.

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

• Submitting a feature or documentation branch for review
• Updating a pull request description with test evidence
• Adding a changelog entry after opening a pull request

Review and install community skills from monitored registries. Check sources, licenses, permissions, and quality; display the full SKILL.md and findings; then install and record the result only after explicit user approval.

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

• Reviewing a community skill before installation
• Checking permissions, network calls, and file changes
• Comparing sources and licenses against an allowlist

Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.

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

• Designing an implementation and QA pair
• Creating a team with development and independent review
• Writing role guidance and team collaboration rules

Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.

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

• Reproducing and fixing broken UI interactions
• Checking desktop and mobile layouts
• Investigating blank pages and console errors

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

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

Use when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and Google stop double-counting"; builds and fixes the measurement plumbing — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — as a pre-flight checklist plus a UTM/event-spec builder. Not for scoring R1/R2 — that is a scored veto in ad-account-auditor; not for account structure — use campaign-architect. 付费广告转化追踪QA/UTM规范/跨平台去重

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

Set up or run design QA gates — token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.

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

Adversarial Quarto-vs-Beamer parity QA. A critic agent compares the Quarto HTML render to the Beamer PDF benchmark for content/visual parity; a fixer agent applies fixes; loops until APPROVED or two consecutive rounds turn up nothing new (fallback cap 5 rounds). Use when user says "qa the quarto", "check parity", "does the html match the pdf?", "quarto matches beamer?", or after a translate-to-quarto run. Requires both the `.qmd` rendered and a `.pdf` benchmark.

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