[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MFYR7GKV183HGG2T2V40C":3,"skill-same:01M71MFYR7GKV183HGG2T2V40C":76},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M71MFYR7GKV183HGG2T2V40C","gds-test-review",null,"Review test quality and coverage. Use when the user says \"test review\" or \"review tests\"","developAgent\u002Fbmad-start","developAgent","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264530239?v=4","01M71J8X6CY24V5ZZHFGETRMSW","01M71J8X739FS28DGQAAY7V4QR",1,"MIT","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.crush\u002Fskills\u002Fgds-test-review\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33],"review","gds test review","test review","test","coverage","when","test quality","tests","use","quality","user","2026-11-10 10:56:23",false,"---\nname: gds-test-review\ndescription: 'Review test quality and coverage. Use when the user says \"test review\" or \"review tests\"'\n---\n\n# Test Review\n\n**Workflow ID**: `gds-test-review`\n**Version**: 1.0 (BMad v6)\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `output_folder`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Goal\n\nReview existing test suite quality, identify coverage gaps, and recommend improvements. Regular test review prevents test rot and maintains test value over time.\n\n## Role\n\nYou are a Game QA Lead with expertise in test suite analysis. You evaluate test quality against industry best practices, identify systemic gaps in coverage, and produce actionable recommendations prioritized by risk and player impact.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow analyzes the existing test suite and produces a comprehensive review report with prioritized action items.\n\n**Primary Output**: `{output_folder}\u002Ftest-review-report.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n- Template: `{installed_path}\u002Ftest-review-template.md`\n\n**Knowledge Base References**:\n- `knowledge\u002Fregression-testing.md`\n- `knowledge\u002Ftest-priorities.md`\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\nreview_scope: \"full\"    # full | targeted | quick\ngame_engine: \"auto\"     # auto | unity | unreal | godot\n```\n\nSearch the project for existing test files and results before proceeding.\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\nVerify before proceeding:\n- Test suite exists (some tests to review)\n- Access to test execution results\n- Understanding of game features\n\n---\n\n### Step 1: Gather Test Suite Metrics\n\n#### Actions\n\n1. **Count Tests by Type**\n\n   | Type                 | Count | Pass Rate | Avg Duration |\n   | -------------------- | ----- | --------- | ------------ |\n   | Unit                 |       |           |              |\n   | Integration          |       |           |              |\n   | Play Mode\u002FFunctional |       |           |              |\n   | Performance          |       |           |              |\n   | **Total**            |       |           |              |\n\n2. **Analyze Test Results**\n   - Recent pass rate (last 10 runs)\n   - Flaky tests (inconsistent results)\n   - Slow tests (> 30s individual)\n   - Disabled\u002Fskipped tests\n\n3. **Map Coverage**\n   - Features with tests\n   - Features without tests\n   - Critical paths covered\n\n---\n\n### Step 2: Assess Test Quality\n\n#### Quality Criteria\n\nFor each test, evaluate:\n\n| Criterion         | Good                             | Bad                          |\n| ----------------- | -------------------------------- | ---------------------------- |\n| **Deterministic** | Same input = same result         | Flaky, timing-dependent      |\n| **Isolated**      | No shared state                  | Tests affect each other      |\n| **Fast**          | \u003C 5s (unit), \u003C 30s (integration) | Minutes per test             |\n| **Readable**      | Clear intent, good names         | Cryptic, no comments         |\n| **Maintained**    | Up-to-date, passing              | Disabled, stale              |\n| **Valuable**      | Tests real behavior              | Tests implementation details |\n\n#### Anti-Pattern Detection\n\nLook for these common issues:\n\n```\nHard-coded waits:\n   await Task.Delay(5000);        \u002F\u002F Bad\n   await WaitUntil(() => cond);   \u002F\u002F Good\n\nShared test state:\n   static bool wasSetup;          \u002F\u002F Dangerous\n   [SetUp] void Setup() { ... }   \u002F\u002F Good\n\nTesting private implementation:\n   var result = obj.GetPrivateField();   \u002F\u002F Bad\n   var result = obj.PublicBehavior();    \u002F\u002F Good\n\nMissing cleanup:\n   var go = Instantiate(prefab);                     \u002F\u002F Leaks\n   var go = Instantiate(prefab);\n   AddCleanup(() => Destroy(go));                    \u002F\u002F Good\n\nAssertion-free tests:\n   void Test() { DoSomething(); }               \u002F\u002F What does it test?\n   void Test() { DoSomething(); Assert.That(...); }  \u002F\u002F Clear\n```\n\n---\n\n### Step 3: Identify Coverage Gaps\n\n#### Critical Areas to Verify\n\n| Area          | P0 Coverage | P1 Coverage | Gap? |\n| ------------- | ----------- | ----------- | ---- |\n| Core Loop     |             |             |      |\n| Save\u002FLoad     |             |             |      |\n| Progression   |             |             |      |\n| Combat        |             |             |      |\n| UI\u002FMenus      |             |             |      |\n| Multiplayer   |             |             |      |\n| Platform Cert |             |             |      |\n\n#### Gap Identification Process\n\n1. List all game features\n2. Check if each feature has tests\n3. Assess test depth (happy path only vs edge cases)\n4. Prioritize gaps by risk\n\n---\n\n### Step 4: Review Test Infrastructure\n\n#### Framework Health\n\n- [ ] Tests run in CI\n- [ ] Results are visible to team\n- [ ] Failures block deployments\n- [ ] Test data is versioned\n- [ ] Fixtures are reusable\n- [ ] Helpers reduce duplication\n\n#### Maintenance Burden\n\n- How often do tests need updates?\n- Are updates proportional to code changes?\n- Do refactors break tests unnecessarily?\n\n---\n\n### Step 5: Generate Recommendations\n\n#### Priority Matrix\n\n| Finding   | Severity       | Effort         | Recommendation |\n| --------- | -------------- | -------------- | -------------- |\n| {finding} | {High\u002FMed\u002FLow} | {High\u002FMed\u002FLow} | {action}       |\n\n#### Common Recommendations\n\n**For Flaky Tests**:\n- Replace `Thread.Sleep` with explicit waits\n- Add proper synchronization\n- Isolate test state\n\n**For Slow Tests**:\n- Move to nightly builds\n- Optimize test setup\n- Mock expensive dependencies\n\n**For Coverage Gaps**:\n- Prioritize P0\u002FP1 features\n- Add smoke tests first\n- Use test-design workflow\n\n**For Maintenance Issues**:\n- Refactor common patterns\n- Create test utilities\n- Improve documentation\n\n---\n\n### Step 6: Generate Test Review Report\n\nWrite `{output_folder}\u002Ftest-review-report.md` using the `test-review-template.md` structure:\n\n```markdown\n# Test Review Report: {Project Name}\n\n## Executive Summary\n\n- Overall health: {Good\u002FNeeds Work\u002FCritical}\n- Key findings: {3-5 bullet points}\n- Recommended actions: {prioritized list}\n\n## Metrics\n\n### Test Suite Statistics\n\n[Tables from Step 1]\n\n### Recent History\n\n[Pass rates, trends]\n\n## Quality Assessment\n\n### Strengths\n\n- {What's working well}\n\n### Issues Found\n\n| Issue | Severity | Tests Affected | Fix |\n| ----- | -------- | -------------- | --- |\n|       |          |                |     |\n\n## Coverage Analysis\n\n### Current Coverage\n\n[Feature coverage table]\n\n### Critical Gaps\n\n[Prioritized list of missing coverage]\n\n## Recommendations\n\n### Immediate (This Sprint)\n\n1. {Fix critical issues}\n\n### Short-term (This Milestone)\n\n1. {Address major gaps}\n\n### Long-term (Ongoing)\n\n1. {Improve infrastructure}\n\n## Appendix\n\n### Flaky Tests\n\n[List with failure patterns]\n\n### Slow Tests\n\n[List with durations]\n\n### Disabled Tests\n\n[List with reasons]\n```\n\n---\n\n## Review Frequency\n\n| Review Type | Frequency | Scope                   | Owner     |\n| ----------- | --------- | ----------------------- | --------- |\n| Quick Check | Weekly    | Pass rates, flaky tests | QA        |\n| Full Review | Monthly   | Coverage, quality       | Tech Lead |\n| Deep Dive   | Quarterly | Infrastructure, strategy| Team      |\n\n---\n\n## Deliverables\n\n1. **Test Review Report** — Comprehensive analysis\n2. **Action Items** — Prioritized improvements\n3. **Coverage Matrix** — Visual gap identification\n4. **Technical Debt List** — Tests needing refactor\n\n---\n\n## Validation\n\nRefer to `checklist.md` for validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n","# Test Review\n\n**Workflow ID**: `gds-test-review`\n**Version**: 1.0 (BMad v6)\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `output_folder`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Goal\n\nReview existing test suite quality, identify coverage gaps, and recommend improvements. Regular test review prevents test rot and maintains test value over time.\n\n## Role\n\nYou are a Game QA Lead with expertise in test suite analysis. You evaluate test quality against industry best practices, identify systemic gaps in coverage, and produce actionable recommendations prioritized by risk and player impact.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow analyzes the existing test suite and produces a comprehensive review report with prioritized action items.\n\n**Primary Output**: `{output_folder}\u002Ftest-review-report.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n- Template: `{installed_path}\u002Ftest-review-template.md`\n\n**Knowledge Base References**:\n- `knowledge\u002Fregression-testing.md`\n- `knowledge\u002Ftest-priorities.md`\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\nreview_scope: \"full\"    # full | targeted | quick\ngame_engine: \"auto\"     # auto | unity | unreal | godot\n```\n\nSearch the project for existing test files and results before proceeding.\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\nVerify before proceeding:\n- Test suite exists (some tests to review)\n- Access to test execution results\n- Understanding of game features\n\n---\n\n### Step 1: Gather Test Suite Metrics\n\n#### Actions\n\n1. **Count Tests by Type**\n\n   | Type                 | Count | Pass Rate | Avg Duration |\n   | -------------------- | ----- | --------- | ------------ |\n   | Unit                 |       |           |              |\n   | Integration          |       |           |              |\n   | Play Mode\u002FFunctional |       |           |              |\n   | Performance          |       |           |              |\n   | **Total**            |       |           |              |\n\n2. **Analyze Test Results**\n   - Recent pass rate (last 10 runs)\n   - Flaky tests (inconsistent results)\n   - Slow tests (> 30s individual)\n   - Disabled\u002Fskipped tests\n\n3. **Map Coverage**\n   - Features with tests\n   - Features without tests\n   - Critical paths covered\n\n---\n\n### Step 2: Assess Test Quality\n\n#### Quality Criteria\n\nFor each test, evaluate:\n\n| Criterion         | Good                             | Bad                          |\n| ----------------- | -------------------------------- | ---------------------------- |\n| **Deterministic** | Same input = same result         | Flaky, timing-dependent      |\n| **Isolated**      | No shared state                  | Tests affect each other      |\n| **Fast**          | \u003C 5s (unit), \u003C 30s (integration) | Minutes per test             |\n| **Readable**      | Clear intent, good names         | Cryptic, no comments         |\n| **Maintained**    | Up-to-date, passing              | Disabled, stale              |\n| **Valuable**      | Tests real behavior              | Tests implementation details |\n\n#### Anti-Pattern Detection\n\nLook for these common issues:\n\n```\nHard-coded waits:\n   await Task.Delay(5000);        \u002F\u002F Bad\n   await WaitUntil(() => cond);   \u002F\u002F Good\n\nShared test state:\n   static bool wasSetup;          \u002F\u002F Dangerous\n   [SetUp] void Setup() { ... }   \u002F\u002F Good\n\nTesting private implementation:\n   var result = obj.GetPrivateField();   \u002F\u002F Bad\n   var result = obj.PublicBehavior();    \u002F\u002F Good\n\nMissing cleanup:\n   var go = Instantiate(prefab);                     \u002F\u002F Leaks\n   var go = Instantiate(prefab);\n   AddCleanup(() => Destroy(go));                    \u002F\u002F Good\n\nAssertion-free tests:\n   void Test() { DoSomething(); }               \u002F\u002F What does it test?\n   void Test() { DoSomething(); Assert.That(...); }  \u002F\u002F Clear\n```\n\n---\n\n### Step 3: Identify Coverage Gaps\n\n#### Critical Areas to Verify\n\n| Area          | P0 Coverage | P1 Coverage | Gap? |\n| ------------- | ----------- | ----------- | ---- |\n| Core Loop     |             |             |      |\n| Save\u002FLoad     |             |             |      |\n| Progression   |             |             |      |\n| Combat        |             |             |      |\n| UI\u002FMenus      |             |             |      |\n| Multiplayer   |             |             |      |\n| Platform Cert |             |             |      |\n\n#### Gap Identification Process\n\n1. List all game features\n2. Check if each feature has tests\n3. Assess test depth (happy path only vs edge cases)\n4. Prioritize gaps by risk\n\n---\n\n### Step 4: Review Test Infrastructure\n\n#### Framework Health\n\n- [ ] Tests run in CI\n- [ ] Results are visible to team\n- [ ] Failures block deployments\n- [ ] Test data is versioned\n- [ ] Fixtures are reusable\n- [ ] Helpers reduce duplication\n\n#### Maintenance Burden\n\n- How often do tests need updates?\n- Are updates proportional to code changes?\n- Do refactors break tests unnecessarily?\n\n---\n\n### Step 5: Generate Recommendations\n\n#### Priority Matrix\n\n| Finding   | Severity       | Effort         | Recommendation |\n| --------- | -------------- | -------------- | -------------- |\n| {finding} | {High\u002FMed\u002FLow} | {High\u002FMed\u002FLow} | {action}       |\n\n#### Common Recommendations\n\n**For Flaky Tests**:\n- Replace `Thread.Sleep` with explicit waits\n- Add proper synchronization\n- Isolate test state\n\n**For Slow Tests**:\n- Move to nightly builds\n- Optimize test setup\n- Mock expensive dependencies\n\n**For Coverage Gaps**:\n- Prioritize P0\u002FP1 features\n- Add smoke tests first\n- Use test-design workflow\n\n**For Maintenance Issues**:\n- Refactor common patterns\n- Create test utilities\n- Improve documentation\n\n---\n\n### Step 6: Generate Test Review Report\n\nWrite `{output_folder}\u002Ftest-review-report.md` using the `test-review-template.md` structure:\n\n```markdown\n# Test Review Report: {Project Name}\n\n## Executive Summary\n\n- Overall health: {Good\u002FNeeds Work\u002FCritical}\n- Key findings: {3-5 bullet points}\n- Recommended actions: {prioritized list}\n\n## Metrics\n\n### Test Suite Statistics\n\n[Tables from Step 1]\n\n### Recent History\n\n[Pass rates, trends]\n\n## Quality Assessment\n\n### Strengths\n\n- {What's working well}\n\n### Issues Found\n\n| Issue | Severity | Tests Affected | Fix |\n| ----- | -------- | -------------- | --- |\n|       |          |                |     |\n\n## Coverage Analysis\n\n### Current Coverage\n\n[Feature coverage table]\n\n### Critical Gaps\n\n[Prioritized list of missing coverage]\n\n## Recommendations\n\n### Immediate (This Sprint)\n\n1. {Fix critical issues}\n\n### Short-term (This Milestone)\n\n1. {Address major gaps}\n\n### Long-term (Ongoing)\n\n1. {Improve infrastructure}\n\n## Appendix\n\n### Flaky Tests\n\n[List with failure patterns]\n\n### Slow Tests\n\n[List with durations]\n\n### Disabled Tests\n\n[List with reasons]\n```\n\n---\n\n## Review Frequency\n\n| Review Type | Frequency | Scope                   | Owner     |\n| ----------- | --------- | ----------------------- | --------- |\n| Quick Check | Weekly    | Pass rates, flaky tests | QA        |\n| Full Review | Monthly   | Coverage, quality       | Tech Lead |\n| Deep Dive   | Quarterly | Infrastructure, strategy| Team      |\n\n---\n\n## Deliverables\n\n1. **Test Review Report** — Comprehensive analysis\n2. **Action Items** — Prioritized improvements\n3. **Coverage Matrix** — Visual gap identification\n4. **Technical Debt List** — Tests needing refactor\n\n---\n\n## Validation\n\nRefer to `checklist.md` for validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n",{"name":5,"description":7},"main","1907bbe850fb749efa8b499b8da7ebb78a663519",".crush\u002Fskills\u002Fgds-test-review",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add developAgent\u002Fbmad-start --skill gds-test-review",{"tool":52,"command":53},"bunx","bunx skills add developAgent\u002Fbmad-start --skill gds-test-review",{"tool":55,"command":56},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill gds-test-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.crush\u002Fskills\u002Fgds-test-review\u002FSKILL.md",true,[60,66,72],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"checklist.md","REFERENCE","参考文档",1555,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.crush\u002Fskills\u002Fgds-test-review\u002Fchecklist.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"customize.toml","OTHER","其他",1641,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.crush\u002Fskills\u002Fgds-test-review\u002Fcustomize.toml",{"path":73,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":74,"sourceHtmlUrl":75},"test-review-template.md",5936,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.crush\u002Fskills\u002Fgds-test-review\u002Ftest-review-template.md",[77,98,127,145,159,185],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":97},"01M71R3M9DJTTY0ARFQ6K04NMP","gds-correct-course","Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-correct-course\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[89,90,91,33,92,93,28,31,94,95,96],"gds correct course","course","correct","changes","change","execution","manage","sprint","2026-11-10 13:02:02",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":110,"publishedAt":97},"01M71R3GENSFD1A1XVZTTQG1KF","gds-code-review","Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says \"run code review\" or \"review this code\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-code-review\u002FSKILL.md",[104,107],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":108,"categoryName":109,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000030","开发工程师",[111,112,23,113,114,92,115,116,117,118,119,120,121,28,122,31,123,124,125,126],"code review","code","gds code review","categories","triage","review code","run","parallel","case","with","run code","acceptance","edge","actionable","layers","hunter",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":97},"01M71R3DD098MQRD6F8S4GG0AW","gds-check-implementation-readiness","Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says \"check readiness\" or \"implementation readiness\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-check-implementation-readiness\u002FSKILL.md",[],[134,135,136,137,138,139,33,140,141,142,143,28,31,144],"check","readiness","Implementation Readiness","gds check implementation readiness","implementation","check readiness","Production","ux","verify","architecture","alignment",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":97},"01M71R3ACAA1G0NVQ330JQNJPK","gds-brainstorm-game","Facilitate game brainstorming sessions with game-specific techniques. Use when the user says \"brainstorm game\" or \"game ideas\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-brainstorm-game\u002FSKILL.md",[],[152,153,154,33,155,120,28,31,156,157,158],"gds brainstorm game","game","brainstorm","brainstorming","techniques","sessions","ideas",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":97},"01M71R377MJ6WJTTFARGKH3HX7","gds-agent-tech-writer","Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-tech-writer\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,170,171,172,31,173,174,175,176,28,33,177,178,179,180,181,182,183,153,184],"gds agent tech writer","tech","writer","technical writer","technical","knowledge","for","projects","technical documentation","talk","specialist","documentation specialist","knowledge curator","requests","documentation","curator",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":97},"01M71R34RGT2ZX3TSFA2CRT0NC","gds-agent-game-solo-dev","Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-game-solo-dev\u002FSKILL.md",[191],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},[193,153,194,195,196,197,33,178,182,198,199,28,31,200,175,201,202],"solo","gds agent game solo dev","dev","flow","developer","RAPID","game developer","prototyping","development","quick"]