[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGFJ8X204HPTA8FZ73HZ1B":3,"skill-same:01M6EGFJ8X204HPTA8FZ73HZ1B":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6EGFJ8X204HPTA8FZ73HZ1B","ln-522-manual-tester",null,"Performs manual testing of Story AC via executable bash scripts saved to tests\u002Fmanual\u002F. Creates reusable test suites per Story.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34],"tester","ln 522 manual tester","testing","test","Bash","Story","reusable","manual testing","tests","scripts","via","2026-11-10 10:12:30",false,"---\nname: ln-522-manual-tester\ndescription: \"Performs manual testing of Story AC via executable bash scripts saved to tests\u002Fmanual\u002F. Creates reusable test suites per Story.\"\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n# Manual Tester\n\nManually verifies Story AC on running code and reports structured results for the quality gate.\n\n## Purpose & Scope\n- Create executable test scripts in `tests\u002Fmanual\u002F` folder of target project.\n- Run AC-driven checks via bash\u002Fcurl (API) or puppeteer (UI).\n- Save scripts permanently for regression testing (not temp files).\n- Document results in Linear with pass\u002Ffail per AC and script path.\n- No status changes or task creation.\n\n## When to Use\n- **Invoked by ln-520-test-planner** after ln-521-test-researcher completes\n- Research comment \"## Test Research:\" exists on Story (from ln-521)\n- All implementation tasks in Story status = Done\n\n## Test Design Principles\n\n### 1. Fail-Fast - No Silent Failures\n\n**CRITICAL:** Tests MUST return 1 (fail) immediately when any criterion is not met.\n\n**Never use:** `print_status \"WARN\" + return 0` for validation failures, graceful degradation without explicit flags, silent fallbacks that hide errors.\n\n**Exceptions (WARN is OK):** Informational warnings that don't affect correctness, optional features (with clear justification in comments), infrastructure issues (e.g., missing Nginx in dev environment).\n\n### 2. Expected-Based Testing - The Golden Standard\n\n**CRITICAL:** Tests MUST compare actual results against **expected reference files**, not apply heuristics or algorithmic checks.\n\n**Directory structure:**\n```\ntests\u002Fmanual\u002FNN-feature\u002F\n├── samples\u002F               # Input files\n├── expected\u002F              # Expected output files (REQUIRED!)\n│   └── {base_name}_{source_lang}-{target_lang}.{ext}\n└── test-*.sh\n```\n\n**Heuristics acceptable ONLY for:** dynamic\u002Fnon-deterministic data (timestamps, UUIDs, tokens - normalize before comparison; JSON with unordered keys - use `jq --sort-keys`).\n\n### 3. Results Storage\n\nTest results saved to `tests\u002Fmanual\u002Fresults\u002F` (persistent, in .gitignore). Named: `result_{ac_name}.{ext}` or `response_{ac_name}.json`. Inspectable after test completion for debugging.\n\n### 4. Expected File Generation\n\nTo create expected files:\n1. Run test with current implementation\n2. Review output in `results\u002F` folder\n3. If correct: copy to `expected\u002F` folder with proper naming\n4. If incorrect: fix implementation first, then copy\n\n**IMPORTANT:** Never blindly copy results to expected. Always validate correctness first.\n\n## Workflow\n\n### Phase 0: Resolve Inputs\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\n1. **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n\n### Phase 1: Setup tests\u002Fmanual structure\n1) **Read `docs\u002Fproject\u002Finfrastructure.md`** — get port allocation, service endpoints, base URLs. **Read `docs\u002Fproject\u002Frunbook.md`** — get Docker commands, test prerequisites, environment setup\n2) Check if `tests\u002Fmanual\u002F` folder exists in project root\n3) If missing, create structure:\n   - `tests\u002Fmanual\u002Fconfig.sh` — shared configuration (BASE_URL, helpers, colors)\n   - `tests\u002Fmanual\u002FREADME.md` — folder documentation (see README.md template below)\n   - `tests\u002Fmanual\u002Ftest-all.sh` — master script to run all test suites (see test-all.sh template below)\n   - `tests\u002Fmanual\u002Fresults\u002F` — folder for test outputs (add to `.gitignore`)\n4) Add `tests\u002Fmanual\u002Fresults\u002F` to project `.gitignore` if not present\n5) If exists, read existing `config.sh` to reuse settings (BASE_URL, tokens)\n\n### Phase 2: Create Story test script\n1) Fetch Story, parse AC into Given\u002FWhen\u002FThen list (3-5 expected)\n   - **Check for research comment** (from ln-521-test-researcher) — incorporate findings into test cases\n2) Detect API vs UI (API → curl, UI → puppeteer). **IF UI:** **MANDATORY READ:** Load `references\u002Fpuppeteer_patterns.md`\n3) Create test folder structure:\n   - `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Fsamples\u002F` — input files (if needed)\n   - `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Fexpected\u002F` — expected output files (REQUIRED for deterministic tests)\n4) Generate test script: `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n   - Use appropriate template: TEMPLATE-api-endpoint.sh (direct calls) or TEMPLATE-document-format.sh (async jobs)\n   - Header: Story ID, AC list, prerequisites\n   - Test function per AC + edge\u002Ferror cases\n   - **diff-based validation** against expected files (PRIMARY)\n   - Results saved to `tests\u002Fmanual\u002Fresults\u002F`\n   - Summary table with timing\n5) Make script executable (`chmod +x`)\n\n### Phase 3: Update Documentation\n1) Update `tests\u002Fmanual\u002FREADME.md`:\n   - Add new test to \"Available Test Suites\" table\n   - Include Story ID, AC covered, run command\n2) Update `tests\u002Fmanual\u002Ftest-all.sh`:\n   - Add call to new script in SUITES array\n   - Maintain execution order (00-setup first, then numbered suites)\n\n### Phase 4: Execute and report\n\n**MANDATORY READ:** Load `references\u002Ftest_result_format_v1.md`\n\n1) Rebuild Docker containers (no cache), ensure healthy\n2) Run generated script, capture output\n3) Parse results (pass\u002Ffail counts)\n4) Post Linear comment (per test_result_format_v1.md) with:\n   - AC matrix (pass\u002Ffail per AC)\n   - Script path: `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n   - Rerun command: `cd tests\u002Fmanual && .\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n\n## Critical Rules\n- Scripts saved to project `tests\u002Fmanual\u002F`, NOT temp files.\n- Rebuild Docker before testing; fail if rebuild\u002Frun unhealthy.\n- Keep language of Story (EN\u002FRU) in script comments and Linear comment.\n- No fixes or status changes; only evidence and verdict.\n- Script must be idempotent (can rerun anytime).\n\n## Definition of Done\n- `tests\u002Fmanual\u002F` structure exists (config.sh, README.md, test-all.sh, results\u002F created if missing).\n- `tests\u002Fmanual\u002Fresults\u002F` added to project `.gitignore`.\n- Test script created at `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`.\n- `expected\u002F` folder created with at least 1 expected file per deterministic AC.\n- Script uses **diff-based validation** against expected files (not heuristics).\n- Script saves results to `tests\u002Fmanual\u002Fresults\u002F` for debugging.\n- Script is executable and idempotent.\n- **README.md updated** with new test suite in \"Available Test Suites\" table.\n- **test-all.sh updated** with call to new script in SUITES array.\n- App rebuilt and running; tests executed.\n- Verdict and Linear comment posted with script path and rerun command.\n\n## Script Templates\n\n### README.md (created once per project)\n\n```markdown\n# Manual Testing Scripts\n\n> **SCOPE:** Bash scripts for manual API testing. Complements automated tests with CLI-based workflows.\n\n## Quick Start\n\n```bash\ncd tests\u002Fmanual\n.\u002F00-setup\u002Fcreate-account.sh  # (if auth required)\n.\u002Ftest-all.sh                 # Run ALL test suites\n```\n\n## Prerequisites\n\n- Docker containers running (`docker compose ps`)\n- jq installed (`apt-get install jq` or `brew install jq`)\n\n## Folder Structure\n\n```\ntests\u002Fmanual\u002F\n├── config.sh          # Shared configuration (BASE_URL, helpers, colors)\n├── README.md          # This file\n├── test-all.sh        # Run all test suites\n├── 00-setup\u002F          # Account & token setup (if auth required)\n│   ├── create-account.sh\n│   └── get-token.sh\n└── {NN}-{topic}\u002F      # Test suites by Story\n    └── test-{slug}.sh\n```\n\n## Available Test Suites\n\n\u003C!-- Add new test suites here when creating new tests -->\n\n| Suite | Story | AC Covered | Run Command |\n|-------|-------|------------|-------------|\n| — | — | — | — |\n\n## Adding New Tests\n\n1. Create script in `{NN}-{topic}\u002Ftest-{slug}.sh`\n2. **Update this README** (Available Test Suites table)\n3. **Update `test-all.sh`** (add to SUITES array)\n```\n\n### test-all.sh (created once per project)\n\n```bash\n#!\u002Fbin\u002Fbash\n# =============================================================================\n# Run all manual test suites\n# =============================================================================\nset -e\nSCRIPT_DIR=\"$(cd \"$(dirname \"${BASH_SOURCE[0]}\")\" && pwd)\"\nsource \"$SCRIPT_DIR\u002Fconfig.sh\"\n\necho \"==========================================\"\necho \"Running ALL Manual Test Suites\"\necho \"==========================================\"\n\ncheck_jq\ncheck_api\n\n# Setup (if exists)\n[ -f \"$SCRIPT_DIR\u002F00-setup\u002Fcreate-account.sh\" ] && \"$SCRIPT_DIR\u002F00-setup\u002Fcreate-account.sh\"\n[ -f \"$SCRIPT_DIR\u002F00-setup\u002Fget-token.sh\" ] && \"$SCRIPT_DIR\u002F00-setup\u002Fget-token.sh\"\n\n# Test suites (add new suites here)\nSUITES=(\n    # \"01-auth\u002Ftest-auth-flow.sh\"\n    # \"02-translation\u002Ftest-translation.sh\"\n)\n\nPASSED=0; FAILED=0\nfor suite in \"${SUITES[@]}\"; do\n    echo \"\"\n    echo \"==========================================\"\n    echo \"Running: $suite\"\n    echo \"==========================================\"\n    if \"$SCRIPT_DIR\u002F$suite\"; then\n        ((++PASSED))\n        print_status \"PASS\" \"$suite\"\n    else\n        ((++FAILED))\n        print_status \"FAIL\" \"$suite\"\n    fi\ndone\n\necho \"\"\necho \"==========================================\"\necho \"TOTAL: $PASSED suites passed, $FAILED failed\"\necho \"==========================================\"\n[ $FAILED -eq 0 ] && exit 0 || exit 1\n```\n\n### config.sh (created once per project)\n\n```bash\n#!\u002Fbin\u002Fbash\n# Shared configuration for manual testing scripts\nexport BASE_URL=\"${BASE_URL:-http:\u002F\u002Flocalhost:8080}\"\nexport RED='\\033[0;31m'\nexport GREEN='\\033[0;32m'\nexport YELLOW='\\033[1;33m'\nexport NC='\\033[0m'\n\nprint_status() {\n    local status=$1; local message=$2\n    case $status in\n        \"PASS\") echo -e \"${GREEN}[PASS]${NC} $message\" ;;\n        \"FAIL\") echo -e \"${RED}[FAIL]${NC} $message\" ;;\n        \"WARN\") echo -e \"${YELLOW}[WARN]${NC} $message\" ;;\n        \"INFO\") echo -e \"[INFO] $message\" ;;\n    esac\n}\n\ncheck_jq() {\n    command -v jq &> \u002Fdev\u002Fnull || { echo \"Error: jq required\"; exit 1; }\n}\n\ncheck_api() {\n    local response=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"$BASE_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull)\n    if [ \"$response\" != \"200\" ]; then\n        echo \"Error: API not reachable at $BASE_URL\"\n        exit 1\n    fi\n    print_status \"INFO\" \"API reachable at $BASE_URL\"\n}\n\nSCRIPT_DIR=\"$(cd \"$(dirname \"${BASH_SOURCE[0]}\")\" && pwd)\"\nexport SCRIPT_DIR\n```\n\n### Test Script Templates\n\n**See:** [references\u002Ftemplates\u002F](references\u002Ftemplates\u002F)\n\n| Template | Use Case | Location |\n|----------|----------|----------|\n| template-api-endpoint.sh | API endpoint tests (NO async jobs) | [template-api-endpoint.sh](references\u002Ftemplates\u002Ftemplate-api-endpoint.sh) |\n| template-document-format.sh | Document\u002Ffile processing (WITH async jobs) | [template-document-format.sh](references\u002Ftemplates\u002Ftemplate-document-format.sh) |\n\n**Quick start:**\n```bash\ncp references\u002Ftemplates\u002Ftemplate-api-endpoint.sh {NN}-feature\u002Ftest-{feature}.sh      # Endpoint tests\ncp references\u002Ftemplates\u002Ftemplate-document-format.sh {NN}-feature\u002Ftest-{format}.sh    # Document tests\n```\n\n## Reference Files\n- Script format reference: prompsit-api `tests\u002Fmanual\u002F` (production example)\n- AC format: `shared\u002Ftemplates\u002Ftest_task_template.md` (or local `docs\u002Ftemplates\u002F` in target project)\n- Risk-based context: `shared\u002Freferences\u002Frisk_based_testing_guide.md`\n- Research findings: ln-521-test-researcher creates \"## Test Research\" comment on Story\n- Puppeteer patterns: `references\u002Fpuppeteer_patterns.md`\n- Test result format: `references\u002Ftest_result_format_v1.md`\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-01-15\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n# Manual Tester\n\nManually verifies Story AC on running code and reports structured results for the quality gate.\n\n## Purpose & Scope\n- Create executable test scripts in `tests\u002Fmanual\u002F` folder of target project.\n- Run AC-driven checks via bash\u002Fcurl (API) or puppeteer (UI).\n- Save scripts permanently for regression testing (not temp files).\n- Document results in Linear with pass\u002Ffail per AC and script path.\n- No status changes or task creation.\n\n## When to Use\n- **Invoked by ln-520-test-planner** after ln-521-test-researcher completes\n- Research comment \"## Test Research:\" exists on Story (from ln-521)\n- All implementation tasks in Story status = Done\n\n## Test Design Principles\n\n### 1. Fail-Fast - No Silent Failures\n\n**CRITICAL:** Tests MUST return 1 (fail) immediately when any criterion is not met.\n\n**Never use:** `print_status \"WARN\" + return 0` for validation failures, graceful degradation without explicit flags, silent fallbacks that hide errors.\n\n**Exceptions (WARN is OK):** Informational warnings that don't affect correctness, optional features (with clear justification in comments), infrastructure issues (e.g., missing Nginx in dev environment).\n\n### 2. Expected-Based Testing - The Golden Standard\n\n**CRITICAL:** Tests MUST compare actual results against **expected reference files**, not apply heuristics or algorithmic checks.\n\n**Directory structure:**\n```\ntests\u002Fmanual\u002FNN-feature\u002F\n├── samples\u002F               # Input files\n├── expected\u002F              # Expected output files (REQUIRED!)\n│   └── {base_name}_{source_lang}-{target_lang}.{ext}\n└── test-*.sh\n```\n\n**Heuristics acceptable ONLY for:** dynamic\u002Fnon-deterministic data (timestamps, UUIDs, tokens - normalize before comparison; JSON with unordered keys - use `jq --sort-keys`).\n\n### 3. Results Storage\n\nTest results saved to `tests\u002Fmanual\u002Fresults\u002F` (persistent, in .gitignore). Named: `result_{ac_name}.{ext}` or `response_{ac_name}.json`. Inspectable after test completion for debugging.\n\n### 4. Expected File Generation\n\nTo create expected files:\n1. Run test with current implementation\n2. Review output in `results\u002F` folder\n3. If correct: copy to `expected\u002F` folder with proper naming\n4. If incorrect: fix implementation first, then copy\n\n**IMPORTANT:** Never blindly copy results to expected. Always validate correctness first.\n\n## Workflow\n\n### Phase 0: Resolve Inputs\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\n1. **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n\n### Phase 1: Setup tests\u002Fmanual structure\n1) **Read `docs\u002Fproject\u002Finfrastructure.md`** — get port allocation, service endpoints, base URLs. **Read `docs\u002Fproject\u002Frunbook.md`** — get Docker commands, test prerequisites, environment setup\n2) Check if `tests\u002Fmanual\u002F` folder exists in project root\n3) If missing, create structure:\n   - `tests\u002Fmanual\u002Fconfig.sh` — shared configuration (BASE_URL, helpers, colors)\n   - `tests\u002Fmanual\u002FREADME.md` — folder documentation (see README.md template below)\n   - `tests\u002Fmanual\u002Ftest-all.sh` — master script to run all test suites (see test-all.sh template below)\n   - `tests\u002Fmanual\u002Fresults\u002F` — folder for test outputs (add to `.gitignore`)\n4) Add `tests\u002Fmanual\u002Fresults\u002F` to project `.gitignore` if not present\n5) If exists, read existing `config.sh` to reuse settings (BASE_URL, tokens)\n\n### Phase 2: Create Story test script\n1) Fetch Story, parse AC into Given\u002FWhen\u002FThen list (3-5 expected)\n   - **Check for research comment** (from ln-521-test-researcher) — incorporate findings into test cases\n2) Detect API vs UI (API → curl, UI → puppeteer). **IF UI:** **MANDATORY READ:** Load `references\u002Fpuppeteer_patterns.md`\n3) Create test folder structure:\n   - `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Fsamples\u002F` — input files (if needed)\n   - `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Fexpected\u002F` — expected output files (REQUIRED for deterministic tests)\n4) Generate test script: `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n   - Use appropriate template: TEMPLATE-api-endpoint.sh (direct calls) or TEMPLATE-document-format.sh (async jobs)\n   - Header: Story ID, AC list, prerequisites\n   - Test function per AC + edge\u002Ferror cases\n   - **diff-based validation** against expected files (PRIMARY)\n   - Results saved to `tests\u002Fmanual\u002Fresults\u002F`\n   - Summary table with timing\n5) Make script executable (`chmod +x`)\n\n### Phase 3: Update Documentation\n1) Update `tests\u002Fmanual\u002FREADME.md`:\n   - Add new test to \"Available Test Suites\" table\n   - Include Story ID, AC covered, run command\n2) Update `tests\u002Fmanual\u002Ftest-all.sh`:\n   - Add call to new script in SUITES array\n   - Maintain execution order (00-setup first, then numbered suites)\n\n### Phase 4: Execute and report\n\n**MANDATORY READ:** Load `references\u002Ftest_result_format_v1.md`\n\n1) Rebuild Docker containers (no cache), ensure healthy\n2) Run generated script, capture output\n3) Parse results (pass\u002Ffail counts)\n4) Post Linear comment (per test_result_format_v1.md) with:\n   - AC matrix (pass\u002Ffail per AC)\n   - Script path: `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n   - Rerun command: `cd tests\u002Fmanual && .\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`\n\n## Critical Rules\n- Scripts saved to project `tests\u002Fmanual\u002F`, NOT temp files.\n- Rebuild Docker before testing; fail if rebuild\u002Frun unhealthy.\n- Keep language of Story (EN\u002FRU) in script comments and Linear comment.\n- No fixes or status changes; only evidence and verdict.\n- Script must be idempotent (can rerun anytime).\n\n## Definition of Done\n- `tests\u002Fmanual\u002F` structure exists (config.sh, README.md, test-all.sh, results\u002F created if missing).\n- `tests\u002Fmanual\u002Fresults\u002F` added to project `.gitignore`.\n- Test script created at `tests\u002Fmanual\u002F{NN}-{story-slug}\u002Ftest-{story-slug}.sh`.\n- `expected\u002F` folder created with at least 1 expected file per deterministic AC.\n- Script uses **diff-based validation** against expected files (not heuristics).\n- Script saves results to `tests\u002Fmanual\u002Fresults\u002F` for debugging.\n- Script is executable and idempotent.\n- **README.md updated** with new test suite in \"Available Test Suites\" table.\n- **test-all.sh updated** with call to new script in SUITES array.\n- App rebuilt and running; tests executed.\n- Verdict and Linear comment posted with script path and rerun command.\n\n## Script Templates\n\n### README.md (created once per project)\n\n```markdown\n# Manual Testing Scripts\n\n> **SCOPE:** Bash scripts for manual API testing. Complements automated tests with CLI-based workflows.\n\n## Quick Start\n\n```bash\ncd tests\u002Fmanual\n.\u002F00-setup\u002Fcreate-account.sh  # (if auth required)\n.\u002Ftest-all.sh                 # Run ALL test suites\n```\n\n## Prerequisites\n\n- Docker containers running (`docker compose ps`)\n- jq installed (`apt-get install jq` or `brew install jq`)\n\n## Folder Structure\n\n```\ntests\u002Fmanual\u002F\n├── config.sh          # Shared configuration (BASE_URL, helpers, colors)\n├── README.md          # This file\n├── test-all.sh        # Run all test suites\n├── 00-setup\u002F          # Account & token setup (if auth required)\n│   ├── create-account.sh\n│   └── get-token.sh\n└── {NN}-{topic}\u002F      # Test suites by Story\n    └── test-{slug}.sh\n```\n\n## Available Test Suites\n\n\u003C!-- Add new test suites here when creating new tests -->\n\n| Suite | Story | AC Covered | Run Command |\n|-------|-------|------------|-------------|\n| — | — | — | — |\n\n## Adding New Tests\n\n1. Create script in `{NN}-{topic}\u002Ftest-{slug}.sh`\n2. **Update this README** (Available Test Suites table)\n3. **Update `test-all.sh`** (add to SUITES array)\n```\n\n### test-all.sh (created once per project)\n\n```bash\n#!\u002Fbin\u002Fbash\n# =============================================================================\n# Run all manual test suites\n# =============================================================================\nset -e\nSCRIPT_DIR=\"$(cd \"$(dirname \"${BASH_SOURCE[0]}\")\" && pwd)\"\nsource \"$SCRIPT_DIR\u002Fconfig.sh\"\n\necho \"==========================================\"\necho \"Running ALL Manual Test Suites\"\necho \"==========================================\"\n\ncheck_jq\ncheck_api\n\n# Setup (if exists)\n[ -f \"$SCRIPT_DIR\u002F00-setup\u002Fcreate-account.sh\" ] && \"$SCRIPT_DIR\u002F00-setup\u002Fcreate-account.sh\"\n[ -f \"$SCRIPT_DIR\u002F00-setup\u002Fget-token.sh\" ] && \"$SCRIPT_DIR\u002F00-setup\u002Fget-token.sh\"\n\n# Test suites (add new suites here)\nSUITES=(\n    # \"01-auth\u002Ftest-auth-flow.sh\"\n    # \"02-translation\u002Ftest-translation.sh\"\n)\n\nPASSED=0; FAILED=0\nfor suite in \"${SUITES[@]}\"; do\n    echo \"\"\n    echo \"==========================================\"\n    echo \"Running: $suite\"\n    echo \"==========================================\"\n    if \"$SCRIPT_DIR\u002F$suite\"; then\n        ((++PASSED))\n        print_status \"PASS\" \"$suite\"\n    else\n        ((++FAILED))\n        print_status \"FAIL\" \"$suite\"\n    fi\ndone\n\necho \"\"\necho \"==========================================\"\necho \"TOTAL: $PASSED suites passed, $FAILED failed\"\necho \"==========================================\"\n[ $FAILED -eq 0 ] && exit 0 || exit 1\n```\n\n### config.sh (created once per project)\n\n```bash\n#!\u002Fbin\u002Fbash\n# Shared configuration for manual testing scripts\nexport BASE_URL=\"${BASE_URL:-http:\u002F\u002Flocalhost:8080}\"\nexport RED='\\033[0;31m'\nexport GREEN='\\033[0;32m'\nexport YELLOW='\\033[1;33m'\nexport NC='\\033[0m'\n\nprint_status() {\n    local status=$1; local message=$2\n    case $status in\n        \"PASS\") echo -e \"${GREEN}[PASS]${NC} $message\" ;;\n        \"FAIL\") echo -e \"${RED}[FAIL]${NC} $message\" ;;\n        \"WARN\") echo -e \"${YELLOW}[WARN]${NC} $message\" ;;\n        \"INFO\") echo -e \"[INFO] $message\" ;;\n    esac\n}\n\ncheck_jq() {\n    command -v jq &> \u002Fdev\u002Fnull || { echo \"Error: jq required\"; exit 1; }\n}\n\ncheck_api() {\n    local response=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"$BASE_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull)\n    if [ \"$response\" != \"200\" ]; then\n        echo \"Error: API not reachable at $BASE_URL\"\n        exit 1\n    fi\n    print_status \"INFO\" \"API reachable at $BASE_URL\"\n}\n\nSCRIPT_DIR=\"$(cd \"$(dirname \"${BASH_SOURCE[0]}\")\" && pwd)\"\nexport SCRIPT_DIR\n```\n\n### Test Script Templates\n\n**See:** [references\u002Ftemplates\u002F](references\u002Ftemplates\u002F)\n\n| Template | Use Case | Location |\n|----------|----------|----------|\n| template-api-endpoint.sh | API endpoint tests (NO async jobs) | [template-api-endpoint.sh](references\u002Ftemplates\u002Ftemplate-api-endpoint.sh) |\n| template-document-format.sh | Document\u002Ffile processing (WITH async jobs) | [template-document-format.sh](references\u002Ftemplates\u002Ftemplate-document-format.sh) |\n\n**Quick start:**\n```bash\ncp references\u002Ftemplates\u002Ftemplate-api-endpoint.sh {NN}-feature\u002Ftest-{feature}.sh      # Endpoint tests\ncp references\u002Ftemplates\u002Ftemplate-document-format.sh {NN}-feature\u002Ftest-{format}.sh    # Document tests\n```\n\n## Reference Files\n- Script format reference: prompsit-api `tests\u002Fmanual\u002F` (production example)\n- AC format: `shared\u002Ftemplates\u002Ftest_task_template.md` (or local `docs\u002Ftemplates\u002F` in target project)\n- Risk-based context: `shared\u002Freferences\u002Frisk_based_testing_guide.md`\n- Research findings: ln-521-test-researcher creates \"## Test Research\" comment on Story\n- Puppeteer patterns: `references\u002Fpuppeteer_patterns.md`\n- Test result format: `references\u002Ftest_result_format_v1.md`\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-01-15\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-522-manual-tester",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-522-manual-tester",{"tool":55,"command":56},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-522-manual-tester",{"tool":58,"command":59},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-522-manual-tester","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002FSKILL.md",true,[63,69,75,79,83],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fpuppeteer_patterns.md","REFERENCE","参考文档",9029,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002Freferences\u002Fpuppeteer_patterns.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Ftemplates\u002Ftemplate-api-endpoint.sh","SCRIPT","脚本",4447,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002Freferences\u002Ftemplates\u002Ftemplate-api-endpoint.sh",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ftemplates\u002Ftemplate-document-format.sh",5705,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002Freferences\u002Ftemplates\u002Ftemplate-document-format.sh",{"path":80,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ftest_result_format_v1.md",8038,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-522-manual-tester\u002Freferences\u002Ftest_result_format_v1.md",{"path":84,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":85,"sourceHtmlUrl":86},"templates.md",17742,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fclaude-code-apple-skills\u002Fskills\u002Fgenerators\u002Fsubscription-offers\u002Ftemplates.md",[88,110,145,172,197,225],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":35},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":127,"publishedAt":35},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[116,119,122],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[112,95,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,34,144],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","bulk",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":35},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":35},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[179,180,27,181,182,183,184,185,186,187,188,189,136,190,191,192,193,194,195,196],"oracle","what if oracle","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":206,"publishedAt":35},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[203],{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[207,208,209,210,211,212,213,214,215,216,217,218,219,131,220,221,222,223,224,141],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":241,"publishedAt":35},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[231,234,237,238],{"categoryNo":232,"categoryName":233,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":235,"categoryName":236,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":239,"categoryName":240,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000036","内容创作者",[132,242,243,216,244,245,246,247,28,248,249,163,250,251,252,253,254,255,109,256],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]