[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M799GDRD5GPBE5S3MBEKA9W2":3,"skill-same:01M799GDRD5GPBE5S3MBEKA9W2":55},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M799GDRD5GPBE5S3MBEKA9W2","analyzing-test-coverage",null,"Analyze code coverage metrics and identify untested code paths.\nUse when analyzing untested code or coverage gaps.\nTrigger with phrases like \"analyze coverage\", \"check test coverage\", or \"find untested code\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting--test-coverage-analyzer--analyzing-test-coverage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-test-coverage\ndescription: |\n  Analyze code coverage metrics and identify untested code paths.\n  Use when analyzing untested code or coverage gaps.\n  Trigger with phrases like \"analyze coverage\", \"check test coverage\", or \"find untested code\".\n\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(test:coverage-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\ntags: [testing, analyzing-test]\n---\n# Test Coverage Analyzer\n\n## Current State\n!`ls package.json pyproject.toml Cargo.toml go.mod 2>\u002Fdev\u002Fnull || echo 'No project manifest found'`\n!`node -v 2>\u002Fdev\u002Fnull || python3 --version 2>\u002Fdev\u002Fnull || echo 'No runtime detected'`\n\n## Overview\n\nAnalyze code coverage metrics to identify untested code paths, dead code, and coverage gaps across line, branch, function, and statement dimensions. Supports Istanbul\u002Fnyc (JavaScript\u002FTypeScript), coverage.py (Python), JaCoCo (Java), and Go coverage tools.\n\n## Prerequisites\n\n- Coverage tool installed and configured (Istanbul\u002Fnyc, c8, coverage.py, JaCoCo, or `go test -cover`)\n- Test suite that can run with coverage instrumentation enabled\n- Coverage threshold targets defined (recommended: 80% lines, 70% branches)\n- Coverage output format set to JSON or LCOV for programmatic analysis\n- Git history available for coverage trend comparison\n\n## Instructions\n\n1. Run the test suite with coverage instrumentation enabled:\n   - JavaScript: `npx jest --coverage --coverageReporters=json-summary,lcov`\n   - Python: `pytest --cov=src --cov-report=json --cov-report=term-missing`\n   - Go: `go test -coverprofile=coverage.out .\u002F...`\n   - Java: Configure JaCoCo Maven\u002FGradle plugin with XML report output.\n2. Parse the coverage report and extract per-file metrics:\n   - Line coverage percentage per file.\n   - Branch coverage percentage per file.\n   - Function coverage percentage per file.\n   - Uncovered line ranges (specific line numbers).\n3. Identify critical coverage gaps by prioritizing:\n   - Files with coverage below the threshold (sort ascending by coverage %).\n   - Files with high complexity but low coverage (use cyclomatic complexity if available).\n   - Recently modified files with decreasing coverage trends.\n   - Public API functions and exported modules lacking any tests.\n4. Analyze uncovered branches specifically:\n   - Find `if\u002Felse` blocks where only one branch is tested.\n   - Identify `switch\u002Fcase` statements with missing case coverage.\n   - Locate error handling paths (`catch`, `except`) never exercised.\n   - Check `||` and `&&` short-circuit conditions.\n5. Generate a prioritized action plan:\n   - List top 10 files needing coverage improvement with specific line ranges.\n   - Suggest test scenarios for each uncovered branch.\n   - Estimate effort (small\u002Fmedium\u002Flarge) for each coverage improvement.\n6. Compare current coverage against the previous commit or baseline:\n   - Calculate coverage delta per file.\n   - Flag files where coverage decreased.\n   - Verify new code added since baseline has adequate coverage.\n7. Write coverage enforcement configuration (coverage thresholds in Jest config, `.coveragerc`, or CI checks).\n\n## Output\n\n- Coverage summary report with overall and per-file metrics\n- Prioritized list of uncovered code paths with file:line references\n- Coverage delta report comparing against baseline\n- Suggested test cases for top coverage gaps\n- Coverage threshold configuration file for CI enforcement\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Coverage report shows 0% | Tests ran but coverage instrumentation was not enabled | Verify `--coverage` flag is passed; check that source files are not excluded by config |\n| Coverage includes `node_modules` | Coverage collection scope too broad | Add `collectCoverageFrom` in Jest config; set `--cov=src` in pytest; exclude vendor dirs |\n| Branch coverage much lower than line coverage | Conditional logic is only partially tested | Write tests for both truthy and falsy conditions on each branch; focus on edge cases |\n| Coverage drops after refactor | New code added without corresponding tests | Set `coverageThreshold` with `global` minimums; add `--changedSince` for incremental checks |\n| Flaky coverage numbers between runs | Non-deterministic test execution skipping code paths | Sort tests deterministically; run coverage with `--runInBand` for consistent results |\n\n## Examples\n\n**Jest coverage configuration with thresholds:**\n```json\n{\n  \"jest\": {\n    \"coverageThreshold\": {\n      \"global\": {\n        \"branches\": 70,\n        \"functions\": 80,\n        \"lines\": 80,\n        \"statements\": 80\n      },\n      \"src\u002Futils\u002F\": {\n        \"branches\": 90,\n        \"lines\": 95\n      }\n    },\n    \"collectCoverageFrom\": [\n      \"src\u002F**\u002F*.{ts,tsx}\",\n      \"!src\u002F**\u002F*.d.ts\",\n      \"!src\u002F**\u002Findex.ts\"\n    ]\n  }\n}\n```\n\n**Coverage gap analysis output:**\n```\nCoverage Gaps (sorted by impact):\n1. src\u002Fauth\u002Foauth.ts        Lines: 45%  Branches: 30%  [Lines 42-67, 89-103 uncovered]\n   Suggestion: Add tests for token refresh failure and expired session handling\n2. src\u002Fapi\u002Fmiddleware.ts     Lines: 62%  Branches: 41%  [Lines 28-35, 71-80 uncovered]\n   Suggestion: Test rate limiting edge cases and malformed header handling\n3. src\u002Futils\u002Fparser.ts       Lines: 71%  Branches: 55%  [Lines 112-130 uncovered]\n   Suggestion: Test malformed input, empty string, and encoding edge cases\n```\n\n## Resources\n\n- Istanbul\u002Fnyc: https:\u002F\u002Fistanbul.js.org\u002F\n- c8 (Node.js native coverage): https:\u002F\u002Fgithub.com\u002Fbcoe\u002Fc8\n- coverage.py: https:\u002F\u002Fcoverage.readthedocs.io\u002F\n- JaCoCo: https:\u002F\u002Fwww.jacoco.org\u002Fjacoco\u002F\n- Go test coverage: https:\u002F\u002Fgo.dev\u002Fblog\u002Fcover\n- Code coverage best practices: https:\u002F\u002Ftesting.googleblog.com\u002F2020\u002F08\u002Fcode-coverage-best-practices.html","# Test Coverage Analyzer\n\n## Current State\n!`ls package.json pyproject.toml Cargo.toml go.mod 2>\u002Fdev\u002Fnull || echo 'No project manifest found'`\n!`node -v 2>\u002Fdev\u002Fnull || python3 --version 2>\u002Fdev\u002Fnull || echo 'No runtime detected'`\n\n## Overview\n\nAnalyze code coverage metrics to identify untested code paths, dead code, and coverage gaps across line, branch, function, and statement dimensions. Supports Istanbul\u002Fnyc (JavaScript\u002FTypeScript), coverage.py (Python), JaCoCo (Java), and Go coverage tools.\n\n## Prerequisites\n\n- Coverage tool installed and configured (Istanbul\u002Fnyc, c8, coverage.py, JaCoCo, or `go test -cover`)\n- Test suite that can run with coverage instrumentation enabled\n- Coverage threshold targets defined (recommended: 80% lines, 70% branches)\n- Coverage output format set to JSON or LCOV for programmatic analysis\n- Git history available for coverage trend comparison\n\n## Instructions\n\n1. Run the test suite with coverage instrumentation enabled:\n   - JavaScript: `npx jest --coverage --coverageReporters=json-summary,lcov`\n   - Python: `pytest --cov=src --cov-report=json --cov-report=term-missing`\n   - Go: `go test -coverprofile=coverage.out .\u002F...`\n   - Java: Configure JaCoCo Maven\u002FGradle plugin with XML report output.\n2. Parse the coverage report and extract per-file metrics:\n   - Line coverage percentage per file.\n   - Branch coverage percentage per file.\n   - Function coverage percentage per file.\n   - Uncovered line ranges (specific line numbers).\n3. Identify critical coverage gaps by prioritizing:\n   - Files with coverage below the threshold (sort ascending by coverage %).\n   - Files with high complexity but low coverage (use cyclomatic complexity if available).\n   - Recently modified files with decreasing coverage trends.\n   - Public API functions and exported modules lacking any tests.\n4. Analyze uncovered branches specifically:\n   - Find `if\u002Felse` blocks where only one branch is tested.\n   - Identify `switch\u002Fcase` statements with missing case coverage.\n   - Locate error handling paths (`catch`, `except`) never exercised.\n   - Check `||` and `&&` short-circuit conditions.\n5. Generate a prioritized action plan:\n   - List top 10 files needing coverage improvement with specific line ranges.\n   - Suggest test scenarios for each uncovered branch.\n   - Estimate effort (small\u002Fmedium\u002Flarge) for each coverage improvement.\n6. Compare current coverage against the previous commit or baseline:\n   - Calculate coverage delta per file.\n   - Flag files where coverage decreased.\n   - Verify new code added since baseline has adequate coverage.\n7. Write coverage enforcement configuration (coverage thresholds in Jest config, `.coveragerc`, or CI checks).\n\n## Output\n\n- Coverage summary report with overall and per-file metrics\n- Prioritized list of uncovered code paths with file:line references\n- Coverage delta report comparing against baseline\n- Suggested test cases for top coverage gaps\n- Coverage threshold configuration file for CI enforcement\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Coverage report shows 0% | Tests ran but coverage instrumentation was not enabled | Verify `--coverage` flag is passed; check that source files are not excluded by config |\n| Coverage includes `node_modules` | Coverage collection scope too broad | Add `collectCoverageFrom` in Jest config; set `--cov=src` in pytest; exclude vendor dirs |\n| Branch coverage much lower than line coverage | Conditional logic is only partially tested | Write tests for both truthy and falsy conditions on each branch; focus on edge cases |\n| Coverage drops after refactor | New code added without corresponding tests | Set `coverageThreshold` with `global` minimums; add `--changedSince` for incremental checks |\n| Flaky coverage numbers between runs | Non-deterministic test execution skipping code paths | Sort tests deterministically; run coverage with `--runInBand` for consistent results |\n\n## Examples\n\n**Jest coverage configuration with thresholds:**\n```json\n{\n  \"jest\": {\n    \"coverageThreshold\": {\n      \"global\": {\n        \"branches\": 70,\n        \"functions\": 80,\n        \"lines\": 80,\n        \"statements\": 80\n      },\n      \"src\u002Futils\u002F\": {\n        \"branches\": 90,\n        \"lines\": 95\n      }\n    },\n    \"collectCoverageFrom\": [\n      \"src\u002F**\u002F*.{ts,tsx}\",\n      \"!src\u002F**\u002F*.d.ts\",\n      \"!src\u002F**\u002Findex.ts\"\n    ]\n  }\n}\n```\n\n**Coverage gap analysis output:**\n```\nCoverage Gaps (sorted by impact):\n1. src\u002Fauth\u002Foauth.ts        Lines: 45%  Branches: 30%  [Lines 42-67, 89-103 uncovered]\n   Suggestion: Add tests for token refresh failure and expired session handling\n2. src\u002Fapi\u002Fmiddleware.ts     Lines: 62%  Branches: 41%  [Lines 28-35, 71-80 uncovered]\n   Suggestion: Test rate limiting edge cases and malformed header handling\n3. src\u002Futils\u002Fparser.ts       Lines: 71%  Branches: 55%  [Lines 112-130 uncovered]\n   Suggestion: Test malformed input, empty string, and encoding edge cases\n```\n\n## Resources\n\n- Istanbul\u002Fnyc: https:\u002F\u002Fistanbul.js.org\u002F\n- c8 (Node.js native coverage): https:\u002F\u002Fgithub.com\u002Fbcoe\u002Fc8\n- coverage.py: https:\u002F\u002Fcoverage.readthedocs.io\u002F\n- JaCoCo: https:\u002F\u002Fwww.jacoco.org\u002Fjacoco\u002F\n- Go test coverage: https:\u002F\u002Fgo.dev\u002Fblog\u002Fcover\n- Code coverage best practices: https:\u002F\u002Ftesting.googleblog.com\u002F2020\u002F08\u002Fcode-coverage-best-practices.html",{"name":5,"tags":24,"author":27,"license":15,"version":28,"description":29,"allowed-tools":30,"compatible-with":31},[25,26],"testing","analyzing-test","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Analyze code coverage metrics and identify untested code paths.\nUse when analyzing untested code or coverage gaps.\nTrigger with phrases like \"analyze coverage\", \"check test coverage\", or \"find untested code\".\n","Read, Write, Edit, Grep, Glob, Bash(test:coverage-*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Ftesting--test-coverage-analyzer--analyzing-test-coverage",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill analyzing-test-coverage",{"tool":47,"command":48},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill analyzing-test-coverage",{"tool":50,"command":51},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill analyzing-test-coverage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting--test-coverage-analyzer--analyzing-test-coverage\u002FSKILL.md",true,[],[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"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":76,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]