Add skills, hooks and docs for agentic testing

.claude/hooks/approve-commands.sh

@@ -0,0 +1,37 @@
+#!/bin/bash
+
+# This hook automatically approves known-good commands
+# Hook receives tool call details via stdin as JSON
+#
+# Any command containing one of these patterns is approved.
+
+APPROVED_PATTERNS=(
+  'ls'
+  'find'
+  'playwright-cli'
+  'uv run make'
+)
+
+# Read the tool call data
+input=$(cat)
+
+# PreToolUse input uses tool_name and tool_input (see https://code.claude.com/docs/en/hooks)
+tool_name=$(echo "$input" | jq -r '.tool_name // empty')
+command=$(echo "$input" | jq -r '.tool_input.command // empty')
+
+if [[ "$tool_name" != "Bash" ]]; then
+  exit 10
+fi
+
+for pattern in "${APPROVED_PATTERNS[@]}"; do
+  if [[ "$command" == *"$pattern"* ]]; then
+    reason="Command matches approved pattern: $pattern"
+    jq -n \
+      --arg reason "$reason" \
+      '{ hookSpecificOutput: { hookEventName: "PreToolUse", permissionDecision: "allow", permissionDecisionReason: $reason } }'
+    exit 0
+  fi
+done
+
+# Exit 10 means "no decision" - defer to normal approval flow
+exit 10

.claude/settings.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-settings.json",
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": ".claude/hooks/approve-commands.sh"
+          }
+        ]
+      }
+    ]
+  }
+}

.claude/skills/playwright-cli/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: playwright-cli
+description: 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.
+allowed-tools: Bash(playwright-cli:*)
+---
+
+# Browser Automation with playwright-cli
+
+## Quick start
+
+```bash
+playwright-cli open https://playwright.dev
+playwright-cli click e15
+playwright-cli type "page.click"
+playwright-cli press Enter
+```
+
+## Core workflow
+
+1. Navigate: `playwright-cli open https://example.com`
+2. Interact using refs from the snapshot
+3. Re-snapshot after significant changes
+
+## Commands
+
+### Core
+
+```bash
+playwright-cli open https://example.com/
+playwright-cli close
+playwright-cli type "search query"
+playwright-cli click e3
+playwright-cli dblclick e7
+playwright-cli fill e5 "user@example.com"
+playwright-cli drag e2 e8
+playwright-cli hover e4
+playwright-cli select e9 "option-value"
+playwright-cli upload ./document.pdf
+playwright-cli check e12
+playwright-cli uncheck e12
+playwright-cli snapshot
+playwright-cli eval "document.title"
+playwright-cli eval "el => el.textContent" e5
+playwright-cli dialog-accept
+playwright-cli dialog-accept "confirmation text"
+playwright-cli dialog-dismiss
+playwright-cli resize 1920 1080
+```
+
+### Navigation
+
+```bash
+playwright-cli go-back
+playwright-cli go-forward
+playwright-cli reload
+```
+
+### Keyboard
+
+```bash
+playwright-cli press Enter
+playwright-cli press ArrowDown
+playwright-cli keydown Shift
+playwright-cli keyup Shift
+```
+
+### Mouse
+
+```bash
+playwright-cli mousemove 150 300
+playwright-cli mousedown
+playwright-cli mousedown right
+playwright-cli mouseup
+playwright-cli mouseup right
+playwright-cli mousewheel 0 100
+```
+
+### Save as
+
+```bash
+playwright-cli screenshot
+playwright-cli screenshot e5
+playwright-cli pdf
+```
+
+### Tabs
+
+```bash
+playwright-cli tab-list
+playwright-cli tab-new
+playwright-cli tab-new https://example.com/page
+playwright-cli tab-close
+playwright-cli tab-close 2
+playwright-cli tab-select 0
+```
+
+### DevTools
+
+```bash
+playwright-cli console
+playwright-cli console warning
+playwright-cli network
+playwright-cli run-code "async page => await page.context().grantPermissions(['geolocation'])"
+playwright-cli tracing-start
+playwright-cli tracing-stop
+playwright-cli video-start
+playwright-cli video-stop video.webm
+```
+
+### Configuration
+
+```bash
+# Configure the session
+playwright-cli config --config my-config.json
+playwright-cli config --headed --isolated --browser=firefox
+# Configure named session
+playwright-cli --session=mysession config my-config.json
+# Start with configured session
+playwright-cli open --config=my-config.json
+```
+
+### Sessions
+
+```bash
+playwright-cli --session=mysession open example.com
+playwright-cli --session=mysession click e6
+playwright-cli session-list
+playwright-cli session-stop mysession
+playwright-cli session-stop-all
+playwright-cli session-delete
+playwright-cli session-delete mysession
+```
+
+## Example: Form submission
+
+```bash
+playwright-cli open https://example.com/form
+playwright-cli snapshot
+
+playwright-cli fill e1 "user@example.com"
+playwright-cli fill e2 "password123"
+playwright-cli click e3
+playwright-cli snapshot
+```
+
+## Example: Multi-tab workflow
+
+```bash
+playwright-cli open https://example.com
+playwright-cli tab-new https://example.com/other
+playwright-cli tab-list
+playwright-cli tab-select 0
+playwright-cli snapshot
+```
+
+## Example: Debugging with DevTools
+
+```bash
+playwright-cli open https://example.com
+playwright-cli click e4
+playwright-cli fill e7 "test"
+playwright-cli console
+playwright-cli network
+```
+
+```bash
+playwright-cli open https://example.com
+playwright-cli tracing-start
+playwright-cli click e4
+playwright-cli fill e7 "test"
+playwright-cli tracing-stop
+```
+
+## Specific tasks
+
+- **Request mocking** [references/request-mocking.md](references/request-mocking.md)
+- **Running Playwright code** [references/running-code.md](references/running-code.md)
+- **Session management** [references/session-management.md](references/session-management.md)
+- **Storage state (cookies, localStorage)** [references/storage-state.md](references/storage-state.md)
+- **Test generation** [references/test-generation.md](references/test-generation.md)
+- **Tracing** [references/tracing.md](references/tracing.md)
+- **Video recording** [references/video-recording.md](references/video-recording.md)

.claude/skills/release-testing/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: release-testing
+description: Test documentation instructions by working through the page step by step and performing actions using the playwright-cli. Use when the user asks you to test a specific page.
+allowed-tools: Bash(playwright-cli:*)
+---
+
+# Testing documentation pages
+
+When testing documentation pages you should:
+
+- Build a fresh version of the nightly documentation.
+- Locate the page you have been asked to test within the `build` directory (use the `*.html.md` version of the page).
+- Read the instructions on the page.
+- Check the parent directory for another project called `deployment-internal` as it contains additional instructions.
+  - Additional private instructions for using NVIDIA systems are stored in markdown files in this project.
+  - If you cannot find this project than ask the user for it's location.
+  - Before you start testing a page review any related pages in `deployment-internal`.
+- Use the `playwright-cli` tool to drive a browser and follow the instructions (use a headed browser).
+- Provide a report to the user, include:
+  - Full list of compute resources you created.
+  - Any problems you found.
+
+## Goals
+
+- Follow every step of the instructions in the documentation.
+- Track any differences between the documentation and the real world experience.
+- Verify that RAPIDS is installed successfully.
+
+## Instructions
+
+Most of the instructions focus on creating cloud infrastructure by clicking through GUIs on third-party cloud platforms. Some things to focus on:
+
+- If you need to authenticate ask the user to do this for you.
+- If documentation has both GUI and CLI instructions focus on the GUI instructions.
+- Wait for compute resources to launch before continuing.
+- Buttons and menus may change and move around, if you cannot find the exact thing try and find a way to do the same action, note this difference in your report.
+- If a deployment fails or you get an error message ask the user for assistance.
+- If you repeat steps over and over without making progress ask the user for help.
+- Every page should end with a step that verifies RAPIDS is installed and can be used. If this is missing note it in your report.
+- Before performing destructuve actions like deleting a resource always ask the user for confirmation first

.gitignore

@@ -25,6 +25,8 @@ __pycache__
 cufile.log
 node_modules/
 jupyter_execute/
+.playwright-cli/
+.claude/*.local.*
 
 # files manually written by example code
 source/examples/rapids-azureml-hpo/Dockerfile