跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

pinchtab-dev

Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".

pinchtab · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add pinchtab/pinchtab --skill pinchtab-dev

技能说明


name: pinchtab-dev description: Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".

PinchTab Development

PinchTab is a browser control server for AI agents — Small Go binary with HTTP API.

Project Location

cd ~/dev/pinchtab

Dev Commands

All development commands run via ./dev:

CommandDescription
./dev buildBuild the application
./dev devBuild & run
./dev dashboardHot-reload dashboard development (Vite + Go)
./dev runRun the application
./dev checkAll checks (Go + Dashboard + Plugin)
./dev check goGo checks only
./dev check dashboardDashboard checks only
./dev test unitGo unit tests
./dev test dashboardDashboard unit tests
./dev e2e basicBasic suite (api + cli + infra)
./dev e2e extendedExtended suite (all extended)
./dev e2e smokeSmoke suite
./dev e2e smoke-dockerHost Docker smoke checks only
./dev e2e test "<name>"Run a single E2E test by start_test name
./dev allcheck + test + e2e (pre-push gate)
./dev binariesBuild the full release binary matrix into dist/
./dev doctorSetup dev environment

Architecture

cmd/pinchtab/     CLI entry point
internal/
  bridge/         Chrome CDP communication
  handlers/       HTTP API handlers
  server/         HTTP server
  dashboard/      Embedded React dashboard
  config/         Configuration
  assets/         Embedded assets (stealth.js)
dashboard/        React dashboard source (Vite + TypeScript)
tests/e2e/        E2E test suites

Workflow: New Feature or Bug Fix

  1. Create branch from main:

    git checkout main && git pull
    git checkout -b feat/my-feature  # or fix/my-bug
    
  2. Make changes — follow code patterns in existing files

  3. Run checks locally:

    ./dev all          # check + test + e2e (one-shot pre-push gate)
    # …or individually:
    ./dev check        # Lint + format + typecheck
    ./dev test unit    # Go unit tests
    ./dev e2e basic    # E2E tests (Docker required)
    
  4. Commit with conventional commits:

    • feat: new feature
    • fix: bug fix
    • refactor: code change without behavior change
    • test: adding tests
    • docs: documentation
    • chore: maintenance
  5. Push and create PR

Definition of Done (PR Checklist)

Required — Code Quality

  • Error handling explicit — all errors wrapped with %w, no silent failures
  • No regressions — verify stealth, token efficiency, session persistence
  • SOLID principles — functions do one thing, testable
  • No redundant comments — explain why, not what

Required — Testing

  • New/changed functionality has tests
  • Docker E2E tests pass locally: ./dev e2e basic (or ./dev all for the full chain)
  • If npm wrapper touched: npm pack and npm install work

Required — Documentation

  • README.md updated if user-facing changes
  • /docs/ updated if API/architecture changed

Required — Review

  • PR description explains what + why
  • Commits are atomic with good messages

Key Files

FilePurpose
internal/assets/stealth.jsBot detection evasion (light/medium/full levels)
internal/bridge/bridge.goChrome CDP bridge
internal/handlers/*.goHTTP API endpoints
dashboard/src/React dashboard source
tests/e2e/scenarios-api/API E2E tests
tests/e2e/scenarios-cli/CLI E2E tests

Testing

Unit Tests

./dev test unit              # All Go tests
go test ./internal/handlers  # Specific package

E2E Tests (requires Docker)

./dev e2e basic                 # Basic suite (api + cli + infra)
./dev e2e api                   # API basic tests
./dev e2e cli                   # CLI basic tests
./dev e2e infra                 # Infra basic tests
./dev e2e api-extended          # API extended tests (multi-instance)
./dev e2e cli-extended          # CLI extended tests
./dev e2e infra-extended        # Infra extended tests (multi-instance)
./dev e2e extended              # Full extended suite (all extended tests)
./dev e2e smoke-docker          # Host Docker smoke checks only

# Run specific test file(s) with filter (second argument)
./dev e2e api clipboard                # Run only clipboard-basic.sh
./dev e2e api-extended "clipboard|console"  # Run clipboard and console tests
./dev e2e cli browser                  # Run browser-basic.sh in CLI suite

# Run a single test by its start_test name (fastest debug loop)
./dev e2e test "humanClick: click input by ref"
./dev e2e test "scroll (down)"
./dev e2e test "low-level mouse"

The scenario filter is a substring matched against scenario filenames. Requires Docker daemon running.

Single-test mode (dev e2e test "<name>")

Use this when iterating on one specific E2E failure. The runner:

  1. Greps tests/e2e/scenarios/**/*.sh for start_test "...<name substring>...".
  2. Auto-picks the suite (api/cli/infra/plugin) and -extended variant from the matching scenario file's path.
  3. Builds fresh images (compose ... up --build) and runs only the matching start_test...end_test block — the scenario preamble (helper sourcing, FIXTURES_URL, etc.) is preserved, every other test in the file is skipped.

Notes:

  • The substring is literal (fgrep), so colons/parens/quotes in test names work without escaping.
  • If multiple tests match, the runner uses the first and prints the others — pass a longer/more-specific substring to disambiguate.
  • Logs stream to the terminal by default (unlike full suites which hide logs); helpful for debugging.
  • Implemented by scripts/dev-e2e.sh + E2E_TEST_FILTER plumbing through `s
阅读完整来源 ↗