[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F2A9JY52T0FGAFVFD7CGFF":3,"skill-same:01M6F2A9JY52T0FGAFVFD7CGFF":70},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6F2A9JY52T0FGAFVFD7CGFF","tdd-guide",null,"Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftdd-guide\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"guide","tdd guide","tdd","analysis","with","multi","driven","generation","subagents","coverage","engineering","framework","test generation","development","test driven development","coverage analysis","test","support","2026-11-10 10:12:30",false,"---\nname: tdd-guide\ndescription: Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation\n---\n\n# TDD Guide - Test Driven Development for Engineering Teams\n\nA comprehensive Test Driven Development skill that provides intelligent test generation, coverage analysis, framework integration, and TDD workflow guidance across multiple languages and testing frameworks.\n\n## Capabilities\n\n### Test Generation\n- **Generate Test Cases from Requirements**: Convert user stories, API specs, and business requirements into executable test cases\n- **Create Test Stubs**: Generate test function scaffolding with proper naming, imports, and setup\u002Fteardown\n- **Generate Test Fixtures**: Create realistic test data, mocks, and fixtures for various scenarios\n\n### TDD Workflow Support\n- **Guide Red-Green-Refactor**: Step-by-step guidance through TDD cycles with validation\n- **Suggest Missing Scenarios**: Identify untested edge cases, error conditions, and boundary scenarios\n- **Review Test Quality**: Analyze test isolation, assertions quality, naming conventions, and maintainability\n\n### Coverage & Metrics Analysis\n- **Calculate Coverage**: Parse LCOV, JSON, and XML coverage reports for line\u002Fbranch\u002Ffunction coverage\n- **Identify Untested Paths**: Find code paths, branches, and error handlers without test coverage\n- **Recommend Improvements**: Prioritized recommendations (P0\u002FP1\u002FP2) for coverage gaps and test quality\n\n### Framework Integration\n- **Multi-Framework Support**: Jest, Pytest, JUnit, Vitest, Mocha, RSpec adapters\n- **Generate Boilerplate**: Create test files with proper imports, describe blocks, and best practices\n- **Configure Test Runners**: Set up test configuration, coverage tools, and CI integration\n\n### Comprehensive Metrics\n- **Test Coverage**: Line, branch, function coverage with gap analysis\n- **Code Complexity**: Cyclomatic complexity, cognitive complexity, testability scoring\n- **Test Quality**: Assertions per test, isolation score, naming quality, test smell detection\n- **Test Data**: Boundary value analysis, edge case identification, mock data generation\n- **Test Execution**: Timing analysis, slow test detection, flakiness detection\n- **Missing Tests**: Uncovered edge cases, error handling gaps, missing integration scenarios\n\n## Input Requirements\n\nThe skill supports **automatic format detection** for flexible input:\n\n### Source Code\n- **Languages**: TypeScript, JavaScript, Python, Java\n- **Format**: Direct file paths or copy-pasted code blocks\n- **Detection**: Automatic language\u002Fframework detection from syntax and imports\n\n### Test Artifacts\n- **Coverage Reports**: LCOV (.lcov), JSON (coverage-final.json), XML (cobertura.xml)\n- **Test Results**: JUnit XML, Jest JSON, Pytest JSON, TAP format\n- **Format**: File paths or raw coverage data\n\n### Requirements (Optional)\n- **User Stories**: Text descriptions of functionality\n- **API Specifications**: OpenAPI\u002FSwagger, REST endpoints, GraphQL schemas\n- **Business Requirements**: Acceptance criteria, business rules\n\n### Input Methods\n- **Option A**: Provide file paths (skill will read files)\n- **Option B**: Copy-paste code\u002Fdata directly\n- **Option C**: Mix of both (automatically detected)\n\n## Output Formats\n\nThe skill provides **context-aware output** optimized for your environment:\n\n### Code Files\n- **Test Files**: Generated tests (Jest\u002FPytest\u002FJUnit\u002FVitest) with proper structure\n- **Fixtures**: Test data files, mock objects, factory functions\n- **Mocks**: Mock implementations, stub functions, test doubles\n\n### Reports\n- **Markdown**: Rich coverage reports, recommendations, quality analysis (Claude Desktop)\n- **JSON**: Machine-readable metrics, structured data for CI\u002FCD integration\n- **Terminal-Friendly**: Simplified output for Claude Code CLI\n\n### Smart Defaults\n- **Desktop\u002FApps**: Rich markdown with tables, code blocks, visual hierarchy\n- **CLI**: Concise, terminal-friendly format with clear sections\n- **CI\u002FCD**: JSON output for automated processing\n\n### Progressive Disclosure\n- **Summary First**: High-level overview (\u003C200 tokens)\n- **Details on Demand**: Full analysis available (500-1000 tokens)\n- **Prioritized**: P0 (critical) → P1 (important) → P2 (nice-to-have)\n\n## How to Use\n\n### Basic Usage\n```\n@tdd-guide\n\nI need tests for my authentication module. Here's the code:\n[paste code or provide file path]\n\nGenerate comprehensive test cases covering happy path, error cases, and edge cases.\n```\n\n### Coverage Analysis\n```\n@tdd-guide\n\nAnalyze test coverage for my TypeScript project. Coverage report: coverage\u002Flcov.info\n\nIdentify gaps and provide prioritized recommendations.\n```\n\n### TDD Workflow\n```\n@tdd-guide\n\nGuide me through TDD for implementing a password validation function.\n\nRequirements:\n- Min 8 characters\n- At least 1 uppercase, 1 lowercase, 1 number, 1 special char\n- No common passwords\n```\n\n### Multi-Framework Support\n```\n@tdd-guide\n\nConvert these Jest tests to Pytest format:\n[paste Jest tests]\n```\n\n## Scripts\n\n### Core Modules\n\n- **test_generator.py**: Intelligent test case generation from requirements and code\n- **coverage_analyzer.py**: Parse and analyze coverage reports (LCOV, JSON, XML)\n- **metrics_calculator.py**: Calculate comprehensive test and code quality metrics\n- **framework_adapter.py**: Multi-framework adapter (Jest, Pytest, JUnit, Vitest)\n- **tdd_workflow.py**: Red-green-refactor workflow guidance and validation\n- **fixture_generator.py**: Generate realistic test data and fixtures\n- **format_detector.py**: Automatic language and framework detection\n\n### Utilities\n\n- **complexity_analyzer.py**: Cyclomatic and cognitive complexity analysis\n- **test_quality_scorer.py**: Test quality scoring (isolation, assertions, naming)\n- **missing_test_detector.py**: Identify untested paths and missing scenarios\n- **output_formatter.py**: Context-aware output formatting (Desktop vs CLI)\n\n## Best Practices\n\n### Test Generation\n1. **Start with Requirements**: Write tests from user stories before seeing implementation\n2. **Test Behavior, Not Implementation**: Focus on what code does, not how it does it\n3. **One Assertion Focus**: Each test should verify one specific behavior\n4. **Descriptive Names**: Test names should read like specifications\n\n### TDD Workflow\n1. **Red**: Write failing test first\n2. **Green**: Write minimal code to make it pass\n3. **Refactor**: Improve code while keeping tests green\n4. **Repeat**: Small iterations, frequent commits\n\n### Coverage Goals\n1. **Aim for 80%+**: Line coverage baseline for most projects\n2. **100% Critical Paths**: Authentication, payments, data validation must be fully covered\n3. **Branch Coverage Matters**: Line coverage alone is insufficient\n4. **Don't Game Metrics**: Focus on meaningful tests, not coverage numbers\n\n### Test Quality\n1. **Independent Tests**: Each test should run in isolation\n2. **Fast Execution**: Keep unit tests under 100ms each\n3. **Deterministic**: Tests should always produce same results\n4. **Clear Failures**: Assertion messages should explain what went wrong\n\n### Framework Selection\n1. **Jest**: JavaScript\u002FTypeScript projects (React, Node.js)\n2. **Pytest**: Python projects (Django, Flask, FastAPI)\n3. **JUnit**: Java projects (Spring, Android)\n4. **Vitest**: Modern Vite-based projects\n\n## Multi-Language Support\n\n### TypeScript\u002FJavaScript\n- Frameworks: Jest, Vitest, Mocha, Jasmine\n- Runners: Node.js, Karma, Playwright\n- Coverage: Istanbul\u002Fnyc, c8\n\n### Python\n- Frameworks: Pytest, unittest, nose2\n- Runners: pytest, tox, nox\n- Coverage: coverage.py, pytest-cov\n\n### Java\n- Frameworks: JUnit 5, TestNG, Mockito\n- Runners: Maven Surefire, Gradle Test\n- Coverage: JaCoCo, Cobertura\n\n## Limitations\n\n### Scope\n- **Unit Tests Focus**: Primarily optimized for unit tests (integration tests require different patterns)\n- **Static Analysis Only**: Cannot execute tests or measure actual code behavior\n- **Language Support**: Best support for TypeScript, JavaScript, Python, Java (other languages limited)\n\n### Coverage Analysis\n- **Report Dependency**: Requires existing coverage reports (cannot generate coverage from scratch)\n- **Format Support**: LCOV, JSON, XML only (other formats need conversion)\n- **Interpretation Context**: Coverage numbers need human judgment for meaningfulness\n\n### Test Generation\n- **Baseline Quality**: Generated tests provide scaffolding, require human review and refinement\n- **Complex Logic**: Advanced business logic and integration scenarios need manual test design\n- **Mocking Strategy**: Mock\u002Fstub strategies should align with project patterns\n\n### Framework Integration\n- **Configuration Required**: Test runners need proper setup (this skill doesn't modify package.json or pom.xml)\n- **Version Compatibility**: Generated code targets recent stable versions (Jest 29+, Pytest 7+, JUnit 5+)\n\n### When NOT to Use This Skill\n- **E2E Testing**: Use dedicated E2E tools (Playwright, Cypress, Selenium)\n- **Performance Testing**: Use JMeter, k6, or Locust\n- **Security Testing**: Use OWASP ZAP, Burp Suite, or security-focused tools\n- **Manual Testing**: Some scenarios require human exploratory testing\n\n## Example Workflows\n\n### Workflow 1: Generate Tests from Requirements\n```\nInput: User story + API specification\nProcess: Parse requirements → Generate test cases → Create test stubs\nOutput: Complete test files ready for implementation\n```\n\n### Workflow 2: Improve Coverage\n```\nInput: Coverage report + source code\nProcess: Identify gaps → Suggest tests → Generate test code\nOutput: Prioritized test cases for uncovered code\n```\n\n### Workflow 3: TDD New Feature\n```\nInput: Feature requirements\nProcess: Guide red-green-refactor → Validate each step → Suggest refactorings\nOutput: Well-tested feature with clean code\n```\n\n### Workflow 4: Framework Migration\n```\nInput: Tests in Framework A\nProcess: Parse tests → Translate patterns → Generate equivalent tests\nOutput: Tests in Framework B with same coverage\n```\n\n## Integration Points\n\n### CI\u002FCD Integration\n- Parse coverage reports from CI artifacts\n- Generate coverage badges and reports\n- Fail builds on coverage thresholds\n- Track coverage trends over time\n\n### IDE Integration\n- Generate tests for selected code\n- Run coverage analysis on save\n- Highlight untested code paths\n- Quick-fix suggestions for test gaps\n\n### Code Review\n- Validate test coverage in PRs\n- Check test quality standards\n- Identify missing test scenarios\n- Suggest improvements before merge\n\n## Version Support\n\n- **Node.js**: 16+ (Jest 29+, Vitest 0.34+)\n- **Python**: 3.8+ (Pytest 7+)\n- **Java**: 11+ (JUnit 5.9+)\n- **TypeScript**: 4.5+\n\n## Related Skills\n\nThis skill works well with:\n- **code-review**: Validate test quality during reviews\n- **refactoring-assistant**: Maintain tests during refactoring\n- **ci-cd-helper**: Integrate coverage in pipelines\n- **documentation-generator**: Generate test documentation\n\n","# TDD Guide - Test Driven Development for Engineering Teams\n\nA comprehensive Test Driven Development skill that provides intelligent test generation, coverage analysis, framework integration, and TDD workflow guidance across multiple languages and testing frameworks.\n\n## Capabilities\n\n### Test Generation\n- **Generate Test Cases from Requirements**: Convert user stories, API specs, and business requirements into executable test cases\n- **Create Test Stubs**: Generate test function scaffolding with proper naming, imports, and setup\u002Fteardown\n- **Generate Test Fixtures**: Create realistic test data, mocks, and fixtures for various scenarios\n\n### TDD Workflow Support\n- **Guide Red-Green-Refactor**: Step-by-step guidance through TDD cycles with validation\n- **Suggest Missing Scenarios**: Identify untested edge cases, error conditions, and boundary scenarios\n- **Review Test Quality**: Analyze test isolation, assertions quality, naming conventions, and maintainability\n\n### Coverage & Metrics Analysis\n- **Calculate Coverage**: Parse LCOV, JSON, and XML coverage reports for line\u002Fbranch\u002Ffunction coverage\n- **Identify Untested Paths**: Find code paths, branches, and error handlers without test coverage\n- **Recommend Improvements**: Prioritized recommendations (P0\u002FP1\u002FP2) for coverage gaps and test quality\n\n### Framework Integration\n- **Multi-Framework Support**: Jest, Pytest, JUnit, Vitest, Mocha, RSpec adapters\n- **Generate Boilerplate**: Create test files with proper imports, describe blocks, and best practices\n- **Configure Test Runners**: Set up test configuration, coverage tools, and CI integration\n\n### Comprehensive Metrics\n- **Test Coverage**: Line, branch, function coverage with gap analysis\n- **Code Complexity**: Cyclomatic complexity, cognitive complexity, testability scoring\n- **Test Quality**: Assertions per test, isolation score, naming quality, test smell detection\n- **Test Data**: Boundary value analysis, edge case identification, mock data generation\n- **Test Execution**: Timing analysis, slow test detection, flakiness detection\n- **Missing Tests**: Uncovered edge cases, error handling gaps, missing integration scenarios\n\n## Input Requirements\n\nThe skill supports **automatic format detection** for flexible input:\n\n### Source Code\n- **Languages**: TypeScript, JavaScript, Python, Java\n- **Format**: Direct file paths or copy-pasted code blocks\n- **Detection**: Automatic language\u002Fframework detection from syntax and imports\n\n### Test Artifacts\n- **Coverage Reports**: LCOV (.lcov), JSON (coverage-final.json), XML (cobertura.xml)\n- **Test Results**: JUnit XML, Jest JSON, Pytest JSON, TAP format\n- **Format**: File paths or raw coverage data\n\n### Requirements (Optional)\n- **User Stories**: Text descriptions of functionality\n- **API Specifications**: OpenAPI\u002FSwagger, REST endpoints, GraphQL schemas\n- **Business Requirements**: Acceptance criteria, business rules\n\n### Input Methods\n- **Option A**: Provide file paths (skill will read files)\n- **Option B**: Copy-paste code\u002Fdata directly\n- **Option C**: Mix of both (automatically detected)\n\n## Output Formats\n\nThe skill provides **context-aware output** optimized for your environment:\n\n### Code Files\n- **Test Files**: Generated tests (Jest\u002FPytest\u002FJUnit\u002FVitest) with proper structure\n- **Fixtures**: Test data files, mock objects, factory functions\n- **Mocks**: Mock implementations, stub functions, test doubles\n\n### Reports\n- **Markdown**: Rich coverage reports, recommendations, quality analysis (Claude Desktop)\n- **JSON**: Machine-readable metrics, structured data for CI\u002FCD integration\n- **Terminal-Friendly**: Simplified output for Claude Code CLI\n\n### Smart Defaults\n- **Desktop\u002FApps**: Rich markdown with tables, code blocks, visual hierarchy\n- **CLI**: Concise, terminal-friendly format with clear sections\n- **CI\u002FCD**: JSON output for automated processing\n\n### Progressive Disclosure\n- **Summary First**: High-level overview (\u003C200 tokens)\n- **Details on Demand**: Full analysis available (500-1000 tokens)\n- **Prioritized**: P0 (critical) → P1 (important) → P2 (nice-to-have)\n\n## How to Use\n\n### Basic Usage\n```\n@tdd-guide\n\nI need tests for my authentication module. Here's the code:\n[paste code or provide file path]\n\nGenerate comprehensive test cases covering happy path, error cases, and edge cases.\n```\n\n### Coverage Analysis\n```\n@tdd-guide\n\nAnalyze test coverage for my TypeScript project. Coverage report: coverage\u002Flcov.info\n\nIdentify gaps and provide prioritized recommendations.\n```\n\n### TDD Workflow\n```\n@tdd-guide\n\nGuide me through TDD for implementing a password validation function.\n\nRequirements:\n- Min 8 characters\n- At least 1 uppercase, 1 lowercase, 1 number, 1 special char\n- No common passwords\n```\n\n### Multi-Framework Support\n```\n@tdd-guide\n\nConvert these Jest tests to Pytest format:\n[paste Jest tests]\n```\n\n## Scripts\n\n### Core Modules\n\n- **test_generator.py**: Intelligent test case generation from requirements and code\n- **coverage_analyzer.py**: Parse and analyze coverage reports (LCOV, JSON, XML)\n- **metrics_calculator.py**: Calculate comprehensive test and code quality metrics\n- **framework_adapter.py**: Multi-framework adapter (Jest, Pytest, JUnit, Vitest)\n- **tdd_workflow.py**: Red-green-refactor workflow guidance and validation\n- **fixture_generator.py**: Generate realistic test data and fixtures\n- **format_detector.py**: Automatic language and framework detection\n\n### Utilities\n\n- **complexity_analyzer.py**: Cyclomatic and cognitive complexity analysis\n- **test_quality_scorer.py**: Test quality scoring (isolation, assertions, naming)\n- **missing_test_detector.py**: Identify untested paths and missing scenarios\n- **output_formatter.py**: Context-aware output formatting (Desktop vs CLI)\n\n## Best Practices\n\n### Test Generation\n1. **Start with Requirements**: Write tests from user stories before seeing implementation\n2. **Test Behavior, Not Implementation**: Focus on what code does, not how it does it\n3. **One Assertion Focus**: Each test should verify one specific behavior\n4. **Descriptive Names**: Test names should read like specifications\n\n### TDD Workflow\n1. **Red**: Write failing test first\n2. **Green**: Write minimal code to make it pass\n3. **Refactor**: Improve code while keeping tests green\n4. **Repeat**: Small iterations, frequent commits\n\n### Coverage Goals\n1. **Aim for 80%+**: Line coverage baseline for most projects\n2. **100% Critical Paths**: Authentication, payments, data validation must be fully covered\n3. **Branch Coverage Matters**: Line coverage alone is insufficient\n4. **Don't Game Metrics**: Focus on meaningful tests, not coverage numbers\n\n### Test Quality\n1. **Independent Tests**: Each test should run in isolation\n2. **Fast Execution**: Keep unit tests under 100ms each\n3. **Deterministic**: Tests should always produce same results\n4. **Clear Failures**: Assertion messages should explain what went wrong\n\n### Framework Selection\n1. **Jest**: JavaScript\u002FTypeScript projects (React, Node.js)\n2. **Pytest**: Python projects (Django, Flask, FastAPI)\n3. **JUnit**: Java projects (Spring, Android)\n4. **Vitest**: Modern Vite-based projects\n\n## Multi-Language Support\n\n### TypeScript\u002FJavaScript\n- Frameworks: Jest, Vitest, Mocha, Jasmine\n- Runners: Node.js, Karma, Playwright\n- Coverage: Istanbul\u002Fnyc, c8\n\n### Python\n- Frameworks: Pytest, unittest, nose2\n- Runners: pytest, tox, nox\n- Coverage: coverage.py, pytest-cov\n\n### Java\n- Frameworks: JUnit 5, TestNG, Mockito\n- Runners: Maven Surefire, Gradle Test\n- Coverage: JaCoCo, Cobertura\n\n## Limitations\n\n### Scope\n- **Unit Tests Focus**: Primarily optimized for unit tests (integration tests require different patterns)\n- **Static Analysis Only**: Cannot execute tests or measure actual code behavior\n- **Language Support**: Best support for TypeScript, JavaScript, Python, Java (other languages limited)\n\n### Coverage Analysis\n- **Report Dependency**: Requires existing coverage reports (cannot generate coverage from scratch)\n- **Format Support**: LCOV, JSON, XML only (other formats need conversion)\n- **Interpretation Context**: Coverage numbers need human judgment for meaningfulness\n\n### Test Generation\n- **Baseline Quality**: Generated tests provide scaffolding, require human review and refinement\n- **Complex Logic**: Advanced business logic and integration scenarios need manual test design\n- **Mocking Strategy**: Mock\u002Fstub strategies should align with project patterns\n\n### Framework Integration\n- **Configuration Required**: Test runners need proper setup (this skill doesn't modify package.json or pom.xml)\n- **Version Compatibility**: Generated code targets recent stable versions (Jest 29+, Pytest 7+, JUnit 5+)\n\n### When NOT to Use This Skill\n- **E2E Testing**: Use dedicated E2E tools (Playwright, Cypress, Selenium)\n- **Performance Testing**: Use JMeter, k6, or Locust\n- **Security Testing**: Use OWASP ZAP, Burp Suite, or security-focused tools\n- **Manual Testing**: Some scenarios require human exploratory testing\n\n## Example Workflows\n\n### Workflow 1: Generate Tests from Requirements\n```\nInput: User story + API specification\nProcess: Parse requirements → Generate test cases → Create test stubs\nOutput: Complete test files ready for implementation\n```\n\n### Workflow 2: Improve Coverage\n```\nInput: Coverage report + source code\nProcess: Identify gaps → Suggest tests → Generate test code\nOutput: Prioritized test cases for uncovered code\n```\n\n### Workflow 3: TDD New Feature\n```\nInput: Feature requirements\nProcess: Guide red-green-refactor → Validate each step → Suggest refactorings\nOutput: Well-tested feature with clean code\n```\n\n### Workflow 4: Framework Migration\n```\nInput: Tests in Framework A\nProcess: Parse tests → Translate patterns → Generate equivalent tests\nOutput: Tests in Framework B with same coverage\n```\n\n## Integration Points\n\n### CI\u002FCD Integration\n- Parse coverage reports from CI artifacts\n- Generate coverage badges and reports\n- Fail builds on coverage thresholds\n- Track coverage trends over time\n\n### IDE Integration\n- Generate tests for selected code\n- Run coverage analysis on save\n- Highlight untested code paths\n- Quick-fix suggestions for test gaps\n\n### Code Review\n- Validate test coverage in PRs\n- Check test quality standards\n- Identify missing test scenarios\n- Suggest improvements before merge\n\n## Version Support\n\n- **Node.js**: 16+ (Jest 29+, Vitest 0.34+)\n- **Python**: 3.8+ (Pytest 7+)\n- **Java**: 11+ (JUnit 5.9+)\n- **TypeScript**: 4.5+\n\n## Related Skills\n\nThis skill works well with:\n- **code-review**: Validate test quality during reviews\n- **refactoring-assistant**: Maintain tests during refactoring\n- **ci-cd-helper**: Integrate coverage in pipelines\n- **documentation-generator**: Generate test documentation\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftdd-guide",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill tdd-guide",{"tool":62,"command":63},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill tdd-guide",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill tdd-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftdd-guide\u002FSKILL.md",true,[],[71,81,91,100,106,113],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":77,"publishedAt":42},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[76],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[78,79,80],"model","model hierarchy","model hierarchy skill",{"skillNo":82,"name":83,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":87,"publishedAt":42},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[86],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[88,89,90],"MCP","zoom","zoom mcp",{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":42},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[97,98,99,89],"sdk","zoom apps sdk","apps",{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":42},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[102],{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":42},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":42},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[115]]