Menu
CLI testing guidance and patterns. Loaded by /ops/test/cli command or subagents for comprehensive Navigator CLI testing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | cli-testing |
| description | CLI testing guidance and patterns. Loaded by /ops/test/cli command or subagents for comprehensive Navigator CLI testing. |
| compatibility | Requires bun and navigator-server running on :9334 |
| allowed-tools | Read Glob Grep Skill TodoWrite Bash(./.claude/scripts/run-tests.sh *) Bash(nav *) Bash(nav-dev *) |
| metadata | {"author":"outfitter-dev","version":"1.0"} |
Automated stress tests for Navigator CLI.
# Start server
bun run dev
# Run tests
./.claude/scripts/run-tests.sh edge-cases
./.claude/scripts/run-tests.sh --all
.claude/
├── commands/ops/test/cli.md # Command definition
├── scripts/run-tests.sh # Test runner (all logic here)
├── scripts/lib/test-runner-lib.sh # Shared test library
└── skills/cli-testing/SKILL.md # This file
| Category | Tests | What It Validates |
|---|---|---|
edge-cases | 10 | Invalid refs, missing args, exit codes |
error-taxonomy | 5 | Error codes from PR #30 |
markers | 10 | Marker creation from refs, tags, filtering |
.scratch/testing/
├── 20260116-abc12-edge-cases.md # Results table
├── 20260116-abc12-edge-cases-debug.log # Debug output
└── ...
Edit .claude/scripts/run-tests.sh:
# Add a test to existing category
run_test 11 "New test name" "nav command" "expected_pattern" "true" # true = expect error
# Add new category
run_new_category() {
setup_category "new-category"
log "Running new-category tests..."
nav open "$TEST_URL" >/dev/null 2>&1
run_test 1 "Test name" "nav command" "pattern" "false"
# ... more tests
finalize_category
}
Then add to main():
new-category) run_new_category || exit_code=1 ;;
0 - All passed1 - Failures2 - Setup errorSafely sync navigator's agent-browser fork with upstream vercel-labs/agent-browser, analyze changes, and generate integration documentation
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Evaluate upstream changes using Navigator's design frameworks to decide what to adopt, skip, or adapt
MCP testing guidance and patterns. Loaded by /ops/test/mcp command or subagents for comprehensive Navigator MCP server testing.