@atlashub/smartstack-cli 1.5.1 → 1.5.3

package/templates/commands/utils/test-web-config.md

@@ -1,160 +1,160 @@
----
-description: Configure test-web targets from external config file
-argument-hint: [path/to/config.json]
-allowed-tools: Read, Write, AskUserQuestion, Glob
-model: haiku
----
-
-# /test-web:config - Web test configuration
-
-Updates web test configuration from external file.
-
-> **CLAUDE INSTRUCTION:** The `AskUserQuestion({...})` blocks are instructions to use the `AskUserQuestion` tool **interactively**. You MUST execute the tool with these parameters to get user response BEFORE continuing.
-
-## Usage
-
-```
-/test-web:config                     # Ask for file interactively
-/test-web:config path/to/config.json # Load file directly
-```
-
-## Workflow
-
-### 1. Get source file
-
-**If argument provided**: Use given path
-
-**Otherwise**: Ask user
-
-```
-AskUserQuestion:
-  question: "Which configuration file do you want to load?"
-  header: "Config file"
-  options:
-    - label: "Search in project"
-      description: "Glob to find *test-web*.json files"
-    - label: "Enter path"
-      description: "Manually specify file path"
-```
-
-### 2. Validate file
-
-1. Check file exists
-2. Read JSON content
-3. Validate structure (targets, settings)
-
-**Expected structure**:
-
-```json
-{
-  "targets": [
-    {
-      "name": "string (required)",
-      "url": "string (required for fetch)",
-      "query": "string (required for search)",
-      "type": "fetch|search (required)",
-      "expects": {
-        "status": "number (optional)",
-        "contains": ["strings"] "(optional)",
-        "hasResults": "boolean (optional)"
-      }
-    }
-  ],
-  "chrome": {
-    "enabled": "boolean",
-    "targets": [...]
-  },
-  "settings": {
-    "timeout": "number",
-    "retries": "number",
-    "reportPath": "string"
-  }
-}
-```
-
-### 3. Merge or replace
-
-```
-AskUserQuestion:
-  question: "How to apply new configuration?"
-  header: "Mode"
-  options:
-    - label: "Replace"
-      description: "Completely replace existing config"
-    - label: "Merge (add)"
-      description: "Add new targets to existing"
-```
-
-### 4. Apply
-
-1. Read existing [.claude/test-web/config.json](.claude/test-web/config.json)
-2. Apply chosen mode (replace or merge)
-3. Write result
-
-### 5. Confirm
-
-```
-CONFIG UPDATED
-────────────────────────────────
-Source:  {source_file_path}
-Mode:    {replace|merge}
-Targets: {total_count}
-────────────────────────────────
-
-Test now:
-/test-web --quick
-```
-
-## Example source files
-
-### Minimal
-
-```json
-{
-  "targets": [
-    {
-      "name": "My site",
-      "url": "https://example.com",
-      "type": "fetch",
-      "expects": { "status": 200 }
-    }
-  ]
-}
-```
-
-### Complete
-
-```json
-{
-  "targets": [
-    {
-      "name": "API Health",
-      "url": "https://api.example.com/health",
-      "type": "fetch",
-      "expects": {
-        "status": 200,
-        "contains": ["healthy", "ok"]
-      }
-    },
-    {
-      "name": "SEO Check",
-      "query": "site:example.com",
-      "type": "search",
-      "expects": { "hasResults": true }
-    }
-  ],
-  "settings": {
-    "timeout": 60000,
-    "retries": 3
-  }
-}
-```
-
-## Available templates
-
-Configuration templates are available in:
-[templates/test-web/](templates/test-web/)
-
----
-
-User: $ARGUMENTS
+---
+description: Configure test-web targets from external config file
+argument-hint: [path/to/config.json]
+allowed-tools: Read, Write, AskUserQuestion, Glob
+model: haiku
+---
+
+# /test-web:config - Web test configuration
+
+Updates web test configuration from external file.
+
+> **CLAUDE INSTRUCTION:** The `AskUserQuestion({...})` blocks are instructions to use the `AskUserQuestion` tool **interactively**. You MUST execute the tool with these parameters to get user response BEFORE continuing.
+
+## Usage
+
+```
+/test-web:config                     # Ask for file interactively
+/test-web:config path/to/config.json # Load file directly
+```
+
+## Workflow
+
+### 1. Get source file
+
+**If argument provided**: Use given path
+
+**Otherwise**: Ask user
+
+```
+AskUserQuestion:
+  question: "Which configuration file do you want to load?"
+  header: "Config file"
+  options:
+    - label: "Search in project"
+      description: "Glob to find *test-web*.json files"
+    - label: "Enter path"
+      description: "Manually specify file path"
+```
+
+### 2. Validate file
+
+1. Check file exists
+2. Read JSON content
+3. Validate structure (targets, settings)
+
+**Expected structure**:
+
+```json
+{
+  "targets": [
+    {
+      "name": "string (required)",
+      "url": "string (required for fetch)",
+      "query": "string (required for search)",
+      "type": "fetch|search (required)",
+      "expects": {
+        "status": "number (optional)",
+        "contains": ["strings"] "(optional)",
+        "hasResults": "boolean (optional)"
+      }
+    }
+  ],
+  "chrome": {
+    "enabled": "boolean",
+    "targets": [...]
+  },
+  "settings": {
+    "timeout": "number",
+    "retries": "number",
+    "reportPath": "string"
+  }
+}
+```
+
+### 3. Merge or replace
+
+```
+AskUserQuestion:
+  question: "How to apply new configuration?"
+  header: "Mode"
+  options:
+    - label: "Replace"
+      description: "Completely replace existing config"
+    - label: "Merge (add)"
+      description: "Add new targets to existing"
+```
+
+### 4. Apply
+
+1. Read existing [.claude/test-web/config.json](.claude/test-web/config.json)
+2. Apply chosen mode (replace or merge)
+3. Write result
+
+### 5. Confirm
+
+```
+CONFIG UPDATED
+────────────────────────────────
+Source:  {source_file_path}
+Mode:    {replace|merge}
+Targets: {total_count}
+────────────────────────────────
+
+Test now:
+/test-web --quick
+```
+
+## Example source files
+
+### Minimal
+
+```json
+{
+  "targets": [
+    {
+      "name": "My site",
+      "url": "https://example.com",
+      "type": "fetch",
+      "expects": { "status": 200 }
+    }
+  ]
+}
+```
+
+### Complete
+
+```json
+{
+  "targets": [
+    {
+      "name": "API Health",
+      "url": "https://api.example.com/health",
+      "type": "fetch",
+      "expects": {
+        "status": 200,
+        "contains": ["healthy", "ok"]
+      }
+    },
+    {
+      "name": "SEO Check",
+      "query": "site:example.com",
+      "type": "search",
+      "expects": { "hasResults": true }
+    }
+  ],
+  "settings": {
+    "timeout": 60000,
+    "retries": 3
+  }
+}
+```
+
+## Available templates
+
+Configuration templates are available in:
+[templates/test-web/](templates/test-web/)
+
+---
+
+User: $ARGUMENTS

package/templates/commands/utils/test-web.md

@@ -1,151 +1,151 @@
----
-description: Test web accessibility and content validation
-argument-hint: --quick|--chrome|--report|<url>
-allowed-tools: WebFetch, WebSearch, Read, Write, Bash
-model: sonnet
----
-
-# /test-web - Web testing agent
-
-Tests accessibility and content of project web resources.
-
-## Execution Modes
-
-| Mode | Flag | Description |
-|------|------|-------------|
-| Quick | `--quick` | WebFetch only (HTTP 200 + text content) |
-| Chrome | `--chrome` | E2E tests with Claude for Chrome (requires `claude --chrome`) |
-| Report | `--report` | Generates detailed report in reports/ |
-| Full | (default) | Quick + Chrome if available |
-
-## Configuration
-
-Reads configuration from: [.claude/test-web/config.json](.claude/test-web/config.json)
-
-## Workflow
-
-### Quick Mode (--quick)
-
-1. **Load configuration**
-   ```bash
-   cat .claude/test-web/config.json
-   ```
-
-2. **For each target type "fetch"**:
-   - `WebFetch(url, "Verify that the page is accessible and contains: {expects.contains}")`
-   - Check HTTP status (200 expected)
-   - Verify expected content presence
-
-3. **For each target type "search"**:
-   - `WebSearch(query)`
-   - Verify results exist
-
-4. **Report**: Display results in console
-
-### Chrome Mode (--chrome)
-
-**Prerequisites**:
-- "Claude for Chrome" extension installed
-- Max/Pro/Team/Enterprise plan
-- Claude Code launched with: `claude --chrome`
-
-1. **Verify Chrome mode is active**
-2. **For each chrome target**:
-   - Navigate to URL
-   - Execute actions (click, verify, etc.)
-   - Capture screenshots if requested
-
-3. **Report**: Generate report with captures
-
-### Report Mode (--report)
-
-Generates markdown file in [.claude/test-web/reports/](.claude/test-web/reports/):
-
-```markdown
-# Test Web Report - YYYY-MM-DD HH:mm
-
-## Summary
-| Target | Status | Time |
-|--------|--------|------|
-| ... | PASS/FAIL | Xms |
-
-## Details
-### Target Name
-- URL: ...
-- Expected: ...
-- Result: ...
-- Screenshot: (if chrome mode)
-```
-
-## Examples
-
-### Quick test of all configured URLs
-
-```
-/test-web --quick
-```
-
-### E2E test with browser
-
-```bash
-# First launch Claude Code with Chrome
-claude --chrome
-
-# Then execute tests
-/test-web --chrome
-```
-
-### Test specific URL
-
-```
-/test-web https://github.com/SIMON-Atlashub/atlashub-claudecode-cli
-```
-
-### Generate detailed report
-
-```
-/test-web --report
-```
-
-## Output Format
-
-### Success
-
-```
-TEST WEB RESULTS
-────────────────────────────────
-✅ GitHub Repository     200 OK    "README" found
-✅ npm Package           200 OK    "claude-tools" found
-✅ Google Indexation     Results   Found in search
-
-Status: 3/3 PASS
-────────────────────────────────
-```
-
-### Failure
-
-```
-TEST WEB RESULTS
-────────────────────────────────
-✅ GitHub Repository     200 OK    "README" found
-❌ npm Package           404       Package not found
-⚠️ Google Indexation     Results   No relevant results
-
-Status: 1/3 PASS, 1 FAIL, 1 WARNING
-────────────────────────────────
-```
-
-## BA/EPCT Integration
-
-This command can be called automatically in:
-- Phase T (Test) of BA workflow: `/ba:5-verify`
-- Phase T of EPCT workflow
-
-## Sources
-
-- [Anthropic - Claude for Chrome](https://www.anthropic.com/news/claude-for-chrome)
-- [Claude Help Center](https://support.claude.com/en/articles/12012173-getting-started-with-claude-in-chrome)
-
----
-
-User: $ARGUMENTS
+---
+description: Test web accessibility and content validation
+argument-hint: --quick|--chrome|--report|<url>
+allowed-tools: WebFetch, WebSearch, Read, Write, Bash
+model: sonnet
+---
+
+# /test-web - Web testing agent
+
+Tests accessibility and content of project web resources.
+
+## Execution Modes
+
+| Mode | Flag | Description |
+|------|------|-------------|
+| Quick | `--quick` | WebFetch only (HTTP 200 + text content) |
+| Chrome | `--chrome` | E2E tests with Claude for Chrome (requires `claude --chrome`) |
+| Report | `--report` | Generates detailed report in reports/ |
+| Full | (default) | Quick + Chrome if available |
+
+## Configuration
+
+Reads configuration from: [.claude/test-web/config.json](.claude/test-web/config.json)
+
+## Workflow
+
+### Quick Mode (--quick)
+
+1. **Load configuration**
+   ```bash
+   cat .claude/test-web/config.json
+   ```
+
+2. **For each target type "fetch"**:
+   - `WebFetch(url, "Verify that the page is accessible and contains: {expects.contains}")`
+   - Check HTTP status (200 expected)
+   - Verify expected content presence
+
+3. **For each target type "search"**:
+   - `WebSearch(query)`
+   - Verify results exist
+
+4. **Report**: Display results in console
+
+### Chrome Mode (--chrome)
+
+**Prerequisites**:
+- "Claude for Chrome" extension installed
+- Max/Pro/Team/Enterprise plan
+- Claude Code launched with: `claude --chrome`
+
+1. **Verify Chrome mode is active**
+2. **For each chrome target**:
+   - Navigate to URL
+   - Execute actions (click, verify, etc.)
+   - Capture screenshots if requested
+
+3. **Report**: Generate report with captures
+
+### Report Mode (--report)
+
+Generates markdown file in [.claude/test-web/reports/](.claude/test-web/reports/):
+
+```markdown
+# Test Web Report - YYYY-MM-DD HH:mm
+
+## Summary
+| Target | Status | Time |
+|--------|--------|------|
+| ... | PASS/FAIL | Xms |
+
+## Details
+### Target Name
+- URL: ...
+- Expected: ...
+- Result: ...
+- Screenshot: (if chrome mode)
+```
+
+## Examples
+
+### Quick test of all configured URLs
+
+```
+/test-web --quick
+```
+
+### E2E test with browser
+
+```bash
+# First launch Claude Code with Chrome
+claude --chrome
+
+# Then execute tests
+/test-web --chrome
+```
+
+### Test specific URL
+
+```
+/test-web https://github.com/SIMON-Atlashub/atlashub-claudecode-cli
+```
+
+### Generate detailed report
+
+```
+/test-web --report
+```
+
+## Output Format
+
+### Success
+
+```
+TEST WEB RESULTS
+────────────────────────────────
+✅ GitHub Repository     200 OK    "README" found
+✅ npm Package           200 OK    "claude-tools" found
+✅ Google Indexation     Results   Found in search
+
+Status: 3/3 PASS
+────────────────────────────────
+```
+
+### Failure
+
+```
+TEST WEB RESULTS
+────────────────────────────────
+✅ GitHub Repository     200 OK    "README" found
+❌ npm Package           404       Package not found
+⚠️ Google Indexation     Results   No relevant results
+
+Status: 1/3 PASS, 1 FAIL, 1 WARNING
+────────────────────────────────
+```
+
+## BA/EPCT Integration
+
+This command can be called automatically in:
+- Phase T (Test) of BA workflow: `/ba:5-verify`
+- Phase T of EPCT workflow
+
+## Sources
+
+- [Anthropic - Claude for Chrome](https://www.anthropic.com/news/claude-for-chrome)
+- [Claude Help Center](https://support.claude.com/en/articles/12012173-getting-started-with-claude-in-chrome)
+
+---
+
+User: $ARGUMENTS