[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CYB4GDXS6AYFH7NMJRTXP7":3,"skill-same:01M6CYB4GDXS6AYFH7NMJRTXP7":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":13,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6CYB4GDXS6AYFH7NMJRTXP7","test-browser",null,"Run browser tests on pages affected by current PR or branch","The-Rabak\u002Fnaysmith","The-Rabak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44833742?v=4","01M6CY211HB58Y8JNWWEV9FGN1","01M6CY8HJW3TE1AQW1F13PHYB2",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-browser\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28],"test","browser","test browser","pr","run","branch","2026-11-10 10:12:30",false,"---\nname: test-browser\ndescription: Run browser tests on pages affected by current PR or branch\n---\n\n## Arguments\n[branch name or 'current' for current branch]\n\n# Browser Test Command\n\n\u003Ccommand_purpose>Run end-to-end browser tests on pages affected by a PR or branch changes using agent-browser CLI.\u003C\u002Fcommand_purpose>\n\n## CRITICAL: Use agent-browser CLI Only\n\n**DO NOT use Chrome MCP tools (mcp__claude-in-chrome__*).**\n\nThis command uses the `agent-browser` CLI exclusively. The agent-browser CLI is a Bash-based tool from Vercel that runs headless Chromium. It is NOT the same as Chrome browser automation via MCP.\n\nIf you find yourself calling `mcp__claude-in-chrome__*` tools, STOP. Use `agent-browser` Bash commands instead.\n\n## Introduction\n\n\u003Crole>QA Engineer specializing in browser-based end-to-end testing\u003C\u002Frole>\n\nThis command tests affected pages in a real browser, catching issues that unit tests miss:\n- JavaScript integration bugs\n- CSS\u002Flayout regressions\n- User workflow breakages\n- Console errors\n\n## Prerequisites\n\n\u003Crequirements>\n- Local development server running (Docker containers for Laravel, `npm run dev` for frontend)\n- agent-browser CLI installed (see Setup below)\n- Git repository with changes to test\n\u003C\u002Frequirements>\n\n## Setup\n\n**Check installation:**\n```bash\ncommand -v agent-browser >\u002Fdev\u002Fnull 2>&1 && echo \"Installed\" || echo \"NOT INSTALLED\"\n```\n\n**Install if needed:**\n```bash\nnpm install -g agent-browser\nagent-browser install  # Downloads Chromium (~160MB)\n```\n\nSee the `agent-browser` skill for detailed usage.\n\n## Main Tasks\n\n### 0. Verify agent-browser Installation\n\nBefore starting ANY browser testing, verify agent-browser is installed:\n\n```bash\ncommand -v agent-browser >\u002Fdev\u002Fnull 2>&1 && echo \"Ready\" || (echo \"Installing...\" && npm install -g agent-browser && agent-browser install)\n```\n\nIf installation fails, inform the user and stop.\n\n### 1. Ask Browser Mode\n\n\u003Cask_browser_mode>\n\nBefore starting tests, ask user if they want to watch the browser:\n\nUse AskUserQuestion with:\n- Question: \"Do you want to watch the browser tests run?\"\n- Options:\n  1. **Headed (watch)** - Opens visible browser window so you can see tests run\n  2. **Headless (faster)** - Runs in background, faster but invisible\n\nStore the choice and use `--headed` flag when user selects \"Headed\".\n\n\u003C\u002Fask_browser_mode>\n\n### 2. Determine Test Scope\n\n\u003Ctest_target> $ARGUMENTS \u003C\u002Ftest_target>\n\n\u003Cdetermine_scope>\n\n**If 'current' or empty:**\n```bash\ngit diff --name-only main...HEAD\n```\n\n**If branch name provided:**\n```bash\ngit diff --name-only main...[branch]\n```\n\n\u003C\u002Fdetermine_scope>\n\n### 3. Map Files to Routes\n\n\u003Cfile_to_route_mapping>\n\nMap changed files to testable routes:\n\n| File Pattern | Route(s) |\n|-------------|----------|\n| `app\u002FHttp\u002FControllers\u002F*Controller.php` | Corresponding API routes (check `routes\u002Fcomponents\u002F`) |\n| `app\u002FServices\u002F*Service.php` | API routes using those services |\n| `resources\u002Fviews\u002F*.blade.php` | Corresponding web routes |\n| `src\u002Fnuxt\u002F*\u002Fpages\u002F*` | Nuxt page routes (filesystem-based) |\n| `src\u002Fnuxt\u002F*\u002Fcomponents\u002F*` | Pages using those components |\n| `www\u002Fapps\u002F*\u002Fsrc\u002Fcomponents\u002F*` | Vue app pages using those components |\n| `www\u002Fapps\u002F*\u002Fsrc\u002Fpages\u002F*` | Vue app page routes |\n| `src\u002Fnuxt\u002F*\u002Flayouts\u002F*` | All pages (test homepage at minimum) |\n| `src\u002Fnuxt\u002F*\u002Fassets\u002Fscss\u002F*` | Visual regression on key pages |\n\nBuild a list of URLs to test based on the mapping.\n\n\u003C\u002Ffile_to_route_mapping>\n\n### 4. Verify Server is Running\n\n\u003Ccheck_server>\n\nBefore testing, verify the local server is accessible:\n\n```bash\nagent-browser open http:\u002F\u002Flocalhost-3000\nagent-browser snapshot -i\n```\n\nIf server is not running, inform user:\n```markdown\n**Server not running**\n\nPlease start your development server (e.g., `npm run dev`, `docker compose up`, etc.).\n\nThen run `\u002Ftest-browser` again.\n```\n\n\u003C\u002Fcheck_server>\n\n### 5. Test Each Affected Page\n\n\u003Ctest_pages>\n\nFor each affected route, use agent-browser CLI commands (NOT Chrome MCP):\n\n**Step 1: Navigate and capture snapshot**\n```bash\nagent-browser open \"http:\u002F\u002Flocalhost:3000\u002F[route]\"\nagent-browser snapshot -i\n```\n\n**Step 2: For headed mode (visual debugging)**\n```bash\nagent-browser --headed open \"http:\u002F\u002Flocalhost:3000\u002F[route]\"\nagent-browser --headed snapshot -i\n```\n\n**Step 3: Verify key elements**\n- Use `agent-browser snapshot -i` to get interactive elements with refs\n- Page title\u002Fheading present\n- Primary content rendered\n- No error messages visible\n- Forms have expected fields\n\n**Step 4: Test critical interactions**\n```bash\nagent-browser click @e1  # Use ref from snapshot\nagent-browser snapshot -i\n```\n\n**Step 5: Take screenshots**\n```bash\nagent-browser screenshot page-name.png\nagent-browser screenshot --full page-name-full.png  # Full page\n```\n\n\u003C\u002Ftest_pages>\n\n### 6. Human Verification (When Required)\n\n\u003Chuman_verification>\n\nPause for human input when testing touches:\n\n| Flow Type | What to Ask |\n|-----------|-------------|\n| OAuth | \"Please sign in with [provider] and confirm it works\" |\n| Email | \"Check your inbox for the test email and confirm receipt\" |\n| Payments | \"Complete a test purchase in sandbox mode\" |\n| SMS | \"Verify you received the SMS code\" |\n| External APIs | \"Confirm the [service] integration is working\" |\n\nUse AskUserQuestion:\n```markdown\n**Human Verification Needed**\n\nThis test touches the [flow type]. Please:\n1. [Action to take]\n2. [What to verify]\n\nDid it work correctly?\n1. Yes - continue testing\n2. No - describe the issue\n```\n\n\u003C\u002Fhuman_verification>\n\n### 7. Handle Failures\n\n\u003Cfailure_handling>\n\nWhen a test fails:\n\n1. **Document the failure:**\n   - Screenshot the error state: `agent-browser screenshot error.png`\n   - Note the exact reproduction steps\n\n2. **Ask user how to proceed:**\n   ```markdown\n   **Test Failed: [route]**\n\n   Issue: [description]\n   Console errors: [if any]\n\n   How to proceed?\n   1. Fix now - I'll help debug and fix\n   2. Create todo - Add to todos\u002F for later\n   3. Skip - Continue testing other pages\n   ```\n\n3. **If \"Fix now\":**\n   - Investigate the issue\n   - Propose a fix\n   - Apply fix\n   - Re-run the failing test\n\n4. **If \"Create todo\":**\n   - Create `{id}-pending-p1-browser-test-{description}.md`\n   - Continue testing\n\n5. **If \"Skip\":**\n   - Log as skipped\n   - Continue testing\n\n\u003C\u002Ffailure_handling>\n\n### 8. Test Summary\n\n\u003Ctest_summary>\n\nAfter all tests complete, present summary:\n\n```markdown\n## Browser Test Results\n\n**Test Scope:** PR #[number] \u002F [branch name]\n**Server:** http:\u002F\u002Flocalhost-3000\n\n### Pages Tested: [count]\n\n| Route | Status | Notes |\n|-------|--------|-------|\n| `\u002Fusers` | Pass | |\n| `\u002Fsettings` | Pass | |\n| `\u002Fdashboard` | Fail | Console error: [msg] |\n| `\u002Fcheckout` | Skip | Requires payment credentials |\n\n### Console Errors: [count]\n- [List any errors found]\n\n### Human Verifications: [count]\n- OAuth flow: Confirmed\n- Email delivery: Confirmed\n\n### Failures: [count]\n- `\u002Fdashboard` - [issue description]\n\n### Created Todos: [count]\n- `005-pending-p1-browser-test-dashboard-error.md`\n\n### Result: [PASS \u002F FAIL \u002F PARTIAL]\n```\n\n\u003C\u002Ftest_summary>\n\n## Quick Usage Examples\n\n```bash\n# Test current branch changes\n\u002Ftest-browser\n\n# Test specific PR\n\u002Ftest-browser 847\n\n# Test specific branch\n\u002Ftest-browser feature\u002Fnew-dashboard\n```\n\n## agent-browser CLI Reference\n\n**ALWAYS use these Bash commands. NEVER use mcp__claude-in-chrome__* tools.**\n\n```bash\n# Navigation\nagent-browser open \u003Curl>           # Navigate to URL\nagent-browser back                 # Go back\nagent-browser close                # Close browser\n\n# Snapshots (get element refs)\nagent-browser snapshot -i          # Interactive elements with refs (@e1, @e2, etc.)\nagent-browser snapshot -i --json   # JSON output\n\n# Interactions (use refs from snapshot)\nagent-browser click @e1            # Click element\nagent-browser fill @e1 \"text\"      # Fill input\nagent-browser type @e1 \"text\"      # Type without clearing\nagent-browser press Enter          # Press key\n\n# Screenshots\nagent-browser screenshot out.png       # Viewport screenshot\nagent-browser screenshot --full out.png # Full page screenshot\n\n# Headed mode (visible browser)\nagent-browser --headed open \u003Curl>      # Open with visible browser\nagent-browser --headed click @e1       # Click in visible browser\n\n# Wait\nagent-browser wait @e1             # Wait for element\nagent-browser wait 2000            # Wait milliseconds\n```\n","## Arguments\n[branch name or 'current' for current branch]\n\n# Browser Test Command\n\n\u003Ccommand_purpose>Run end-to-end browser tests on pages affected by a PR or branch changes using agent-browser CLI.\u003C\u002Fcommand_purpose>\n\n## CRITICAL: Use agent-browser CLI Only\n\n**DO NOT use Chrome MCP tools (mcp__claude-in-chrome__*).**\n\nThis command uses the `agent-browser` CLI exclusively. The agent-browser CLI is a Bash-based tool from Vercel that runs headless Chromium. It is NOT the same as Chrome browser automation via MCP.\n\nIf you find yourself calling `mcp__claude-in-chrome__*` tools, STOP. Use `agent-browser` Bash commands instead.\n\n## Introduction\n\n\u003Crole>QA Engineer specializing in browser-based end-to-end testing\u003C\u002Frole>\n\nThis command tests affected pages in a real browser, catching issues that unit tests miss:\n- JavaScript integration bugs\n- CSS\u002Flayout regressions\n- User workflow breakages\n- Console errors\n\n## Prerequisites\n\n\u003Crequirements>\n- Local development server running (Docker containers for Laravel, `npm run dev` for frontend)\n- agent-browser CLI installed (see Setup below)\n- Git repository with changes to test\n\u003C\u002Frequirements>\n\n## Setup\n\n**Check installation:**\n```bash\ncommand -v agent-browser >\u002Fdev\u002Fnull 2>&1 && echo \"Installed\" || echo \"NOT INSTALLED\"\n```\n\n**Install if needed:**\n```bash\nnpm install -g agent-browser\nagent-browser install  # Downloads Chromium (~160MB)\n```\n\nSee the `agent-browser` skill for detailed usage.\n\n## Main Tasks\n\n### 0. Verify agent-browser Installation\n\nBefore starting ANY browser testing, verify agent-browser is installed:\n\n```bash\ncommand -v agent-browser >\u002Fdev\u002Fnull 2>&1 && echo \"Ready\" || (echo \"Installing...\" && npm install -g agent-browser && agent-browser install)\n```\n\nIf installation fails, inform the user and stop.\n\n### 1. Ask Browser Mode\n\n\u003Cask_browser_mode>\n\nBefore starting tests, ask user if they want to watch the browser:\n\nUse AskUserQuestion with:\n- Question: \"Do you want to watch the browser tests run?\"\n- Options:\n  1. **Headed (watch)** - Opens visible browser window so you can see tests run\n  2. **Headless (faster)** - Runs in background, faster but invisible\n\nStore the choice and use `--headed` flag when user selects \"Headed\".\n\n\u003C\u002Fask_browser_mode>\n\n### 2. Determine Test Scope\n\n\u003Ctest_target> $ARGUMENTS \u003C\u002Ftest_target>\n\n\u003Cdetermine_scope>\n\n**If 'current' or empty:**\n```bash\ngit diff --name-only main...HEAD\n```\n\n**If branch name provided:**\n```bash\ngit diff --name-only main...[branch]\n```\n\n\u003C\u002Fdetermine_scope>\n\n### 3. Map Files to Routes\n\n\u003Cfile_to_route_mapping>\n\nMap changed files to testable routes:\n\n| File Pattern | Route(s) |\n|-------------|----------|\n| `app\u002FHttp\u002FControllers\u002F*Controller.php` | Corresponding API routes (check `routes\u002Fcomponents\u002F`) |\n| `app\u002FServices\u002F*Service.php` | API routes using those services |\n| `resources\u002Fviews\u002F*.blade.php` | Corresponding web routes |\n| `src\u002Fnuxt\u002F*\u002Fpages\u002F*` | Nuxt page routes (filesystem-based) |\n| `src\u002Fnuxt\u002F*\u002Fcomponents\u002F*` | Pages using those components |\n| `www\u002Fapps\u002F*\u002Fsrc\u002Fcomponents\u002F*` | Vue app pages using those components |\n| `www\u002Fapps\u002F*\u002Fsrc\u002Fpages\u002F*` | Vue app page routes |\n| `src\u002Fnuxt\u002F*\u002Flayouts\u002F*` | All pages (test homepage at minimum) |\n| `src\u002Fnuxt\u002F*\u002Fassets\u002Fscss\u002F*` | Visual regression on key pages |\n\nBuild a list of URLs to test based on the mapping.\n\n\u003C\u002Ffile_to_route_mapping>\n\n### 4. Verify Server is Running\n\n\u003Ccheck_server>\n\nBefore testing, verify the local server is accessible:\n\n```bash\nagent-browser open http:\u002F\u002Flocalhost-3000\nagent-browser snapshot -i\n```\n\nIf server is not running, inform user:\n```markdown\n**Server not running**\n\nPlease start your development server (e.g., `npm run dev`, `docker compose up`, etc.).\n\nThen run `\u002Ftest-browser` again.\n```\n\n\u003C\u002Fcheck_server>\n\n### 5. Test Each Affected Page\n\n\u003Ctest_pages>\n\nFor each affected route, use agent-browser CLI commands (NOT Chrome MCP):\n\n**Step 1: Navigate and capture snapshot**\n```bash\nagent-browser open \"http:\u002F\u002Flocalhost:3000\u002F[route]\"\nagent-browser snapshot -i\n```\n\n**Step 2: For headed mode (visual debugging)**\n```bash\nagent-browser --headed open \"http:\u002F\u002Flocalhost:3000\u002F[route]\"\nagent-browser --headed snapshot -i\n```\n\n**Step 3: Verify key elements**\n- Use `agent-browser snapshot -i` to get interactive elements with refs\n- Page title\u002Fheading present\n- Primary content rendered\n- No error messages visible\n- Forms have expected fields\n\n**Step 4: Test critical interactions**\n```bash\nagent-browser click @e1  # Use ref from snapshot\nagent-browser snapshot -i\n```\n\n**Step 5: Take screenshots**\n```bash\nagent-browser screenshot page-name.png\nagent-browser screenshot --full page-name-full.png  # Full page\n```\n\n\u003C\u002Ftest_pages>\n\n### 6. Human Verification (When Required)\n\n\u003Chuman_verification>\n\nPause for human input when testing touches:\n\n| Flow Type | What to Ask |\n|-----------|-------------|\n| OAuth | \"Please sign in with [provider] and confirm it works\" |\n| Email | \"Check your inbox for the test email and confirm receipt\" |\n| Payments | \"Complete a test purchase in sandbox mode\" |\n| SMS | \"Verify you received the SMS code\" |\n| External APIs | \"Confirm the [service] integration is working\" |\n\nUse AskUserQuestion:\n```markdown\n**Human Verification Needed**\n\nThis test touches the [flow type]. Please:\n1. [Action to take]\n2. [What to verify]\n\nDid it work correctly?\n1. Yes - continue testing\n2. No - describe the issue\n```\n\n\u003C\u002Fhuman_verification>\n\n### 7. Handle Failures\n\n\u003Cfailure_handling>\n\nWhen a test fails:\n\n1. **Document the failure:**\n   - Screenshot the error state: `agent-browser screenshot error.png`\n   - Note the exact reproduction steps\n\n2. **Ask user how to proceed:**\n   ```markdown\n   **Test Failed: [route]**\n\n   Issue: [description]\n   Console errors: [if any]\n\n   How to proceed?\n   1. Fix now - I'll help debug and fix\n   2. Create todo - Add to todos\u002F for later\n   3. Skip - Continue testing other pages\n   ```\n\n3. **If \"Fix now\":**\n   - Investigate the issue\n   - Propose a fix\n   - Apply fix\n   - Re-run the failing test\n\n4. **If \"Create todo\":**\n   - Create `{id}-pending-p1-browser-test-{description}.md`\n   - Continue testing\n\n5. **If \"Skip\":**\n   - Log as skipped\n   - Continue testing\n\n\u003C\u002Ffailure_handling>\n\n### 8. Test Summary\n\n\u003Ctest_summary>\n\nAfter all tests complete, present summary:\n\n```markdown\n## Browser Test Results\n\n**Test Scope:** PR #[number] \u002F [branch name]\n**Server:** http:\u002F\u002Flocalhost-3000\n\n### Pages Tested: [count]\n\n| Route | Status | Notes |\n|-------|--------|-------|\n| `\u002Fusers` | Pass | |\n| `\u002Fsettings` | Pass | |\n| `\u002Fdashboard` | Fail | Console error: [msg] |\n| `\u002Fcheckout` | Skip | Requires payment credentials |\n\n### Console Errors: [count]\n- [List any errors found]\n\n### Human Verifications: [count]\n- OAuth flow: Confirmed\n- Email delivery: Confirmed\n\n### Failures: [count]\n- `\u002Fdashboard` - [issue description]\n\n### Created Todos: [count]\n- `005-pending-p1-browser-test-dashboard-error.md`\n\n### Result: [PASS \u002F FAIL \u002F PARTIAL]\n```\n\n\u003C\u002Ftest_summary>\n\n## Quick Usage Examples\n\n```bash\n# Test current branch changes\n\u002Ftest-browser\n\n# Test specific PR\n\u002Ftest-browser 847\n\n# Test specific branch\n\u002Ftest-browser feature\u002Fnew-dashboard\n```\n\n## agent-browser CLI Reference\n\n**ALWAYS use these Bash commands. NEVER use mcp__claude-in-chrome__* tools.**\n\n```bash\n# Navigation\nagent-browser open \u003Curl>           # Navigate to URL\nagent-browser back                 # Go back\nagent-browser close                # Close browser\n\n# Snapshots (get element refs)\nagent-browser snapshot -i          # Interactive elements with refs (@e1, @e2, etc.)\nagent-browser snapshot -i --json   # JSON output\n\n# Interactions (use refs from snapshot)\nagent-browser click @e1            # Click element\nagent-browser fill @e1 \"text\"      # Fill input\nagent-browser type @e1 \"text\"      # Type without clearing\nagent-browser press Enter          # Press key\n\n# Screenshots\nagent-browser screenshot out.png       # Viewport screenshot\nagent-browser screenshot --full out.png # Full page screenshot\n\n# Headed mode (visible browser)\nagent-browser --headed open \u003Curl>      # Open with visible browser\nagent-browser --headed click @e1       # Click in visible browser\n\n# Wait\nagent-browser wait @e1             # Wait for element\nagent-browser wait 2000            # Wait milliseconds\n```\n",{"name":5,"description":7},"main","b097d394a335a9ec3c8a02d64e111f1a9c96703d",".github\u002Fskills\u002Ftest-browser","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith","https:\u002F\u002Fgithub.com\u002FThe-Rabak","2026-03-04 03:03:05",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add The-Rabak\u002Fnaysmith --skill test-browser",{"tool":46,"command":47},"bunx","bunx skills add The-Rabak\u002Fnaysmith --skill test-browser",{"tool":49,"command":50},"pnpm","pnpm dlx skills add The-Rabak\u002Fnaysmith --skill test-browser","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-browser\u002FSKILL.md",true,[],[55,67,81,94,109,123],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":29},"01M6CYBMHFVAMC4T3J8QFYN42M","workflows-work","Execute work plans efficiently while maintaining quality and finishing features","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-work\u002FSKILL.md",[],[62,63,64,65,66],"workflows work","work","workflows","execute","quality",{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":29},"01M6CYBJ1KP7W3X8HEG49KST9Q","workflows-review","Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-review\u002FSKILL.md",[],[74,64,75,76,77,78,79,80],"workflows review","review","thinking","worktrees","multi-agent","analysis","code",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":29},"01M6CYBEW8DDBXW62Q2CA29BPR","workflows-plan","Transform feature descriptions into well-structured project plans following conventions","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-plan\u002FSKILL.md",[],[64,88,89,90,91,92,93],"workflows plan","plan","project","structured","following conventions","conventions",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":29},"01M6CYBBKAHJJ85JC2PS380TGZ","workflows-compound","Document a recently solved problem to compound your team's knowledge","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-compound\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[104,105,64,106,107,108],"compound","workflows compound","document","knowledge","team",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":29},"01M6CYB9062GMP8VSA7N7PB4NW","workflows-brainstorm","Explore requirements and approaches through collaborative dialogue before planning implementation","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-brainstorm\u002FSKILL.md",[],[116,117,64,118,119,120,121,122],"workflows brainstorm","brainstorm","planning","requirements","explore","implementation","dialogue",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":29},"01M6CYB6S7GKWH62CRV3K79MHW","triage","Triage and categorize findings for the CLI todo system","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[],[125,130,131,132,133],"system","categorize","todo","cli"]