원클릭으로 Manus에서 모든 스킬 실행

browser-integration-codegen

스타29

포크7

업데이트2026년 6월 5일 21:26

Generate browser integration suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters for fixtures, routes, and helper imports.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Flow-Research

Flow-Research/harnessy

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Browser Integration Codegen

Purpose

Generate Playwright-style browser integration suites from structured browser regression scenarios while keeping selector discovery and project adapters explicit and portable.

Required contract

canonical regression source from the active QA profile, typically .jarvis/context/profiles/qa.json
optional adapter metadata from .flow/delivery-profile.json for fixture mappings, route helpers, import shims, and DOM inspection paths
Template paths are resolved from ${AGENTS_SKILLS_ROOT}/browser-integration-codegen/.

Steps

Follow ${AGENTS_SKILLS_ROOT}/browser-integration-codegen/commands/browser-integration-codegen.md exactly.
Run qa ids --profile <qa-profile> first and use the QA profile as the source of truth for browser regression inputs.
Parse only canonical browser scenarios from the QA profile's configured regression sources.
Read the relevant source components and optional DOM inspection artifacts to verify selectors. When selectors, redirects, auth state, or responsive behavior are uncertain, run or request a Playwright walkthrough through /browser-qa before writing assertions.
Generate suite files using delivery-profile adapter data only for imports, fixtures, and project-specific test helpers.
Preserve DB Assert: expectations from the regression spec in the generated test plan. If persistence cannot be asserted in the target environment, leave an explicit TODO or skip reason.
Leave explicit TODOs instead of guessing selectors, DB assertions, or auth setup.

Output

generated .spec.ts suite content or files in the QA-profile-configured browser suites directory
summary of selector certainty, unresolved TODOs, and suite/scenario counts

이 저장소의 다른 Skills

같은 저장소

code-refactorer

Flow-Research/harnessy

Autonomous code refactoring agent that rewrites messy functions, splits large files, removes duplication, improves naming, enforces structure, and preserves behavior.

2026-06-0629

anytype-skill

Flow-Research/harnessy

Interact with Anytype's local REST API to manage spaces, objects, types, properties, tags, lists, and search.

2026-06-0529

api-integration-codegen

Flow-Research/harnessy

Generate API integration test suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters.

2026-06-0529

build-e2e

Flow-Research/harnessy

End-to-end product development orchestrator with human-in-the-loop reviews.

2026-06-0529

context-sync

Flow-Research/harnessy

Safe repo pull/push workflow that targets the repository integration branch, uses deterministic planning, and keeps PRs moving with a bounded autonomous resolution loop.

2026-06-0529

dependency-manager

Flow-Research/harnessy

Plan, verify, and explicitly install skill and script runtime dependencies from Harnessy manifests.

2026-06-0529

name	browser-integration-codegen
description	Generate browser integration suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters for fixtures, routes, and helper imports.
disable-model-invocation	false
allowed-tools	Read, Write, Grep, Glob, Bash, ApplyPatch
argument-hint	[--suite <NN>] [--profile .flow/delivery-profile.json] [--delta] [--inspect-first]

Browser Integration Codegen

Purpose

Generate Playwright-style browser integration suites from structured browser regression scenarios while keeping selector discovery and project adapters explicit and portable.

Required contract

canonical regression source from the active QA profile, typically .jarvis/context/profiles/qa.json
optional adapter metadata from .flow/delivery-profile.json for fixture mappings, route helpers, import shims, and DOM inspection paths
Template paths are resolved from ${AGENTS_SKILLS_ROOT}/browser-integration-codegen/.

Steps

Follow ${AGENTS_SKILLS_ROOT}/browser-integration-codegen/commands/browser-integration-codegen.md exactly.
Run qa ids --profile <qa-profile> first and use the QA profile as the source of truth for browser regression inputs.
Parse only canonical browser scenarios from the QA profile's configured regression sources.
Read the relevant source components and optional DOM inspection artifacts to verify selectors. When selectors, redirects, auth state, or responsive behavior are uncertain, run or request a Playwright walkthrough through /browser-qa before writing assertions.
Generate suite files using delivery-profile adapter data only for imports, fixtures, and project-specific test helpers.
Preserve DB Assert: expectations from the regression spec in the generated test plan. If persistence cannot be asserted in the target environment, leave an explicit TODO or skip reason.
Leave explicit TODOs instead of guessing selectors, DB assertions, or auth setup.

Output

generated .spec.ts suite content or files in the QA-profile-configured browser suites directory
summary of selector certainty, unresolved TODOs, and suite/scenario counts