{"id":"15a9c8c5-659e-4f93-a22f-8c2cbe35581a","entityType":"agent","slug":"clawhub-kyro-ma-unit-test-coverage-helper","name":"Unit Test Coverage Helper","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kyro-ma-unit-test-coverage-helper","canonicalPath":"/agent/clawhub-kyro-ma-unit-test-coverage-helper","generatedAt":"2026-10-10T03:52:56.299Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":null},"description":"Helps with Teams need repeatable help adding useful unit test...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.1K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:unit-test-coverage-helper","sourceUrl":"https://clawhub.ai/kyro-ma/unit-test-coverage-helper","homepage":"https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kyro-ma/unit-test-coverage-helper","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":67,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Unit Test Coverage Helper technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":null},"stars":null,"forks":null,"downloads":2113,"packageName":null,"latestVersion":"0.0.0-20261009-045810","tractionLabel":"2.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:47:51.276Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T18:47:51.277Z","lastCrawledAt":"2026-10-09T18:47:51.276Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T18:47:51.276Z","lastVerifiedAt":null,"highlights":[{"version":"0.0.0-20261009-045810","createdAt":"2026-10-09T05:01:43.691Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Removed the skill-card.md file to streamline documentation. - No changes to core functionality; this release focuses on improving documentation and cleanup.","fileCount":8,"zipByteSize":10042},{"version":"0.20260916.221748","createdAt":"2026-09-16T22:20:04.052Z","changelog":"- Documentation updated: README.md, README.zh-CN.md, and references/requirement-plan.md revised. - skill-card.md file removed. - No functional or workflow changes; update focuses on documentation clarity and cleanup.","fileCount":8,"zipByteSize":10365},{"version":"0.20260911.40430","createdAt":"2026-09-11T04:07:23.926Z","changelog":"- Documentation updates in README and requirement references for improved clarity. - skill-card.md file removed to streamline documentation. - No changes to core logic or functionality.","fileCount":8,"zipByteSize":10538},{"version":"0.20260908.51704","createdAt":"2026-09-08T05:19:42.212Z","changelog":"- Updated documentation: README.md and README.zh-CN.md improved for clarity and organization. - References: requirement-plan.md revised to reflect current planning and evidence details. - Removed redundant file: skill-card.md deleted.","fileCount":8,"zipByteSize":10879},{"version":"0.20260907.40414","createdAt":"2026-09-07T04:06:33.892Z","changelog":"- Updated documentation in README.md, README.zh-CN.md, and references/requirement-plan.md. - Removed outdated skill-card.md file. - No changes to core logic or workflow.","fileCount":8,"zipByteSize":10383},{"version":"0.20260906.40422","createdAt":"2026-09-06T04:07:02.427Z","changelog":"- Documentation updated in README.md and README.zh-CN.md. - Reference requirements and planning details revised in references/requirement-plan.md. - skill-card.md file removed.","fileCount":8,"zipByteSize":10958},{"version":"0.20260905.61641","createdAt":"2026-09-05T06:19:25.645Z","changelog":"- Evidence base updated: requirement now supported by 12 signals across 3 source families (was 2). - Demand score increased to 100/100, reflecting higher validated demand and feasibility. - All documentation updated to match new evidence, including skill description and requirement details. - Removed obsolete skill-card.md file.","fileCount":8,"zipByteSize":10496},{"version":"0.20260904.60001","createdAt":"2026-09-04T06:04:10.937Z","changelog":"- Evidence sources updated from 3 source families to 2; demand score adjusted to 90/100. - Updated supporting information in SKILL.md, README.md, and references/requirement-plan.md to reflect these changes. - Removed obsolete file: skill-card.md. - Content and descriptions revised for clarity and alignment with current evidence.","fileCount":8,"zipByteSize":10020}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:unit-test-coverage-helper","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:unit-test-coverage-helper` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/kyro-ma/unit-test-coverage-helper before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T03:52:56.297Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-unit-test-coverage-helper/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":null},"readme":"Skill: Unit Test Coverage Helper\n\nOwner: kyro-ma\n\nSummary: Helps with Teams need repeatable help adding useful unit test...\n\nTags: latest:0.20260916.221748\n\nVersion history:\n\nv0.0.0-20261009-045810 | 2026-10-09T05:01:43.691Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Removed the skill-card.md file to streamline documentation.\n- No changes to core functionality; this release focuses on improving documentation and cleanup.\n\nv0.20260916.221748 | 2026-09-16T22:20:04.052Z | auto\n\n- Documentation updated: README.md, README.zh-CN.md, and references/requirement-plan.md revised.\n- skill-card.md file removed.\n- No functional or workflow changes; update focuses on documentation clarity and cleanup.\n\nv0.20260911.40430 | 2026-09-11T04:07:23.926Z | auto\n\n- Documentation updates in README and requirement references for improved clarity.\n- skill-card.md file removed to streamline documentation.\n- No changes to core logic or functionality.\n\nv0.20260908.51704 | 2026-09-08T05:19:42.212Z | auto\n\n- Updated documentation: README.md and README.zh-CN.md improved for clarity and organization.\n- References: requirement-plan.md revised to reflect current planning and evidence details.\n- Removed redundant file: skill-card.md deleted.\n\nv0.20260907.40414 | 2026-09-07T04:06:33.892Z | auto\n\n- Updated documentation in README.md, README.zh-CN.md, and references/requirement-plan.md.\n- Removed outdated skill-card.md file.\n- No changes to core logic or workflow.\n\nv0.20260906.40422 | 2026-09-06T04:07:02.427Z | auto\n\n- Documentation updated in README.md and README.zh-CN.md.\n- Reference requirements and planning details revised in references/requirement-plan.md.\n- skill-card.md file removed.\n\nv0.20260905.61641 | 2026-09-05T06:19:25.645Z | auto\n\n- Evidence base updated: requirement now supported by 12 signals across 3 source families (was 2).\n- Demand score increased to 100/100, reflecting higher validated demand and feasibility.\n- All documentation updated to match new evidence, including skill description and requirement details.\n- Removed obsolete skill-card.md file.\n\nv0.20260904.60001 | 2026-09-04T06:04:10.937Z | auto\n\n- Evidence sources updated from 3 source families to 2; demand score adjusted to 90/100.\n- Updated supporting information in SKILL.md, README.md, and references/requirement-plan.md to reflect these changes.\n- Removed obsolete file: skill-card.md.\n- Content and descriptions revised for clarity and alignment with current evidence.\n\nv0.20260831.40551 | 2026-08-31T04:08:08.110Z | auto\n\n- Updated documentation: improved clarity and added details in README.md and README.zh-CN.md.\n- Expanded reference material in references/requirement-plan.md.\n- Removed legacy documentation file skill-card.md for simplification.\n\nv0.20260830.92238 | 2026-08-30T09:26:01.152Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Improved requirement plan details in references/requirement-plan.md.\n- Removed skill-card.md to reduce duplication and keep documentation streamlined.\n\nv0.20260829.40354 | 2026-08-29T04:06:30.219Z | auto\n\n- Documentation refreshed: README.md and README.zh-CN.md updated for clarity and consistency.\n- Improved reference organization: references/requirement-plan.md revised.\n- Minor cleanup: skill-card.md file removed.\n\nv0.20260828.40337 | 2026-08-28T04:07:29.177Z | auto\n\n- Documentation updates in main and Chinese README files for improved clarity.\n- Requirement plan reference updated for consistency.\n- Unused skill-card.md file removed for simplification.\n- No changes to core workflow or functionality.\n\nv0.20260827.40448 | 2026-08-27T04:07:17.113Z | auto\n\n- Documentation updated: README.md and README.zh-CN.md revised for clarity.\n- Requirement plan reference updated in references/requirement-plan.md.\n- Removed skill-card.md for simplification.\n- No functional changes to the skill logic or workflow.\n\nv0.20260826.40329 | 2026-08-26T04:06:03.973Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Removed the outdated skill-card.md file.\n- No changes to skill logic; workflow and requirements remain the same.\n\nv0.20260824.40429 | 2026-08-24T04:07:19.340Z | auto\n\n- Source evidence updated from 4 to 3 source families across all documentation and descriptions.\n- Removed the file skill-card.md.\n- Minor text edits for consistency in descriptive files.\n- No changes to core workflow or user interactions.\n\nv0.20260823.40325 | 2026-08-23T04:06:22.401Z | auto\n\n- Source evidence now includes 4 source families (up from 3) supporting the validated demand for unit test coverage help.\n- Updated supporting files and documentation to reflect the new evidence count and families.\n- Removed deprecated skill-card.md file for simplification.\n- No user-facing command or workflow changes; functionality remains consistent.\n\nv0.20260822.135636 | 2026-08-22T13:59:20.868Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Removed the outdated skill-card.md file to reduce redundancy.\n- No changes to core functionality; this release focuses on improving project documentation.\n\nv0.20260812.40408 | 2026-08-12T04:12:24.030Z | auto\n\n- Documentation updated in README.md and README.zh-CN.md for clarity and better guidance.\n- The requirement plan reference was revised in references/requirement-plan.md.\n- The outdated skill-card.md file was removed for better maintainability.\n\nv0.20260811.40534 | 2026-08-11T04:07:41.155Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Requirement planning details refined in references/requirement-plan.md.\n- Removed unnecessary skill-card.md file to streamline the repository.\n\nv0.20260809.40514 | 2026-08-09T04:08:23.098Z | auto\n\n- Documentation improvements in README.md and README.zh-CN.md.\n- Updated references/requirement-plan.md for planning and evidence clarity.\n- Removed obsolete skill-card.md file.\n- No changes to skill functionality.\n\nv0.20260730.110348 | 2026-07-30T11:10:16.498Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Modified references/requirement-plan.md to better reflect current planning details and evidence.\n- Removed the skill-card.md file for simplification and to reduce redundancy.\n\nv0.20260730.10356 | 2026-07-30T01:11:57.768Z | auto\n\n- Requirement evidence updated to reference 3 source families instead of 2; demand score raised to 100/100 in documentation.\n- Minor license and score info adjusted in SKILL.md and all language variants.\n- All documentation files refreshed to reflect new evidence level.\n- Deprecated skill-card.md file removed.\n\nv0.20260730.3907 | 2026-07-30T00:43:15.032Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md with updated planning or review criteria.\n- Removed obsolete skill-card.md file.\n\nv0.20260729.111836 | 2026-07-29T11:26:41.194Z | auto\n\n- Reduced supporting evidence families from 3 to 2; updated demand score and description accordingly.\n- Adjusted demand score from 100/100 to 90/100 to reflect new evidence.\n- Updated supporting documentation to match revised evidence and requirements.\n- Removed the obsolete skill-card.md file.\n\nv0.20260727.4640 | 2026-07-27T00:48:56.863Z | auto\n\n- Updated demand signals to reflect 3 source families instead of 2.\n- Increased demand score from 90/100 to 100/100 based on new evidence.\n- Removed the file skill-card.md for cleanup.\n- Minor metadata and description adjustments to match updated validation and evidence.\n\nv0.20260726.120312 | 2026-07-26T12:11:44.822Z | auto\n\n- Demand evidence updated from 3 to 2 source families; demand score adjusted from 100/100 to 90/100.\n- References in SKILL.md and description updated to reflect evidence from 2 source families.\n- Removed file: skill-card.md.\n- Documentation updated for consistency in both English and Chinese readme files.\n\nv0.20260726.70315 | 2026-07-26T07:05:40.649Z | auto\n\n- Updated documentation (README.md, README.zh-CN.md) for clarity and completeness.\n- Revised or added references/requirement-plan.md for improved planning and review detail.\n- Removed skill-card.md to streamline files and reduce redundancy.\n\nv0.20260726.13716 | 2026-07-26T01:44:57.947Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and guidance.\n- Revised references/requirement-plan.md with current planning and review criteria.\n- Removed obsolete skill-card.md file to streamline documentation.\n\nv0.20260725.34436 | 2026-07-25T03:50:45.667Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md with more detail.\n- Removed obsolete file: skill-card.md.\n\nv0.1.0 | 2026-06-20T13:16:31.310Z | auto\n\nunit-test-coverage-helper 0.1.0\n\n- Initial release providing guided support for adding unit tests and improving test coverage in existing codebases.\n- Includes a step-by-step workflow for requirement gathering, implementation, and validation.\n- Supplies tailored outputs, checklists, and verification notes based on user needs.\n- Designed to be accessible for local hardware and repeatable for team workflows.\n- Triggers on keywords and phrases related to unit testing, test coverage, and software quality.\n\nArchive index:\n\nArchive v0.0.0-20261009-045810: 8 files, 10042 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3059b), README.zh-CN.md (3067b), references/requirement-plan.md (4908b), skill-card.md (1542b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (160b)\n\nFile v0.0.0-20261009-045810:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.0.0-20261009-045810:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn: [Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues: [feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues: [Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues: [Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search: [Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search: [Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search: [Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues: [Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.0.0-20261009-045810:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522103691\n}\n\nFile v0.0.0-20261009-045810:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-10-07T11:54:36+00:00): [Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn (2026-10-07T18:11:28+00:00): [Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues (2026-10-09T03:57:56+00:00): [feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues (2026-10-08T01:19:12+00:00): [Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues (2026-10-08T20:52:07+00:00): [Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search (2026-10-03T19:16:41+00:00): [Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search (2026-10-03T11:12:24+00:00): [Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search (2026-09-26T13:48:45+00:00): [Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues (2026-10-08T11:57:24+00:00): [Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [typescript](https://segmentfault.com/t/typescript)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.0.0-20261009-045810:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn：[Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues：[feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues：[Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues：[Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search：[Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search：[Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search：[Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues：[Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.0.0-20261009-045810:skill-card.md\n\n## Description:\n\nHelps developers and QA teams add useful unit tests and improve coverage in existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nSoftware maintainers, QA engineers, and development teams use this skill to plan and add unit tests, improve coverage, and check that changes preserve existing behavior.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad testing requests may invoke the skill unexpectedly.\n\nMitigation: Confirm the skill is relevant before following its suggestions.\n\nRisk: Suggested code or tests may not match the project's behavior.\n\nMitigation: Review proposed changes and run the relevant test suite before applying them.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Guidance]\n\n**Output Format:** [Markdown with code or shell snippets when relevant]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include a reusable testing checklist and verification notes.]\n\n## Skill Version(s):\n\n0.0.0-20261009-045810 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.0.0-20261009-045810:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.0.0-20261009-045810:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260916.221748: 8 files, 10365 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3137b), README.zh-CN.md (3145b), references/requirement-plan.md (5007b), skill-card.md (1866b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (156b)\n\nFile v0.20260916.221748:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260916.221748:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Publishing prevention: authoritative calendar validation and stale-preview release guard](https://github.com/usdimpact/usd-impact-site/issues/558)\n- github-issues: [WebUI: continuous performance and stability study with real-Gateway evidence](https://github.com/openclaw/openclaw/issues/149361)\n- hacker-news-ask-hn: [LLM based CI pipeline code generator for DSCI](https://news.ycombinator.com/item?id=49728085)\n- hacker-news-search: [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues: [[Admin] Reproduce duty-period management screens](https://github.com/Osiris-Balonga/wanzila/issues/49)\n- github-issues: [Expose live Jupyter cell outputs through read-notebook](https://github.com/luke-m-selway/vscode-live-bridge/issues/5)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n- segmentfault-search: [Android自动化测试一 UiAutomator官方介绍](https://segmentfault.com/a/1190000045114982)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260916.221748:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260916.221748\",\n  \"publishedAt\": 1789597204052\n}\n\nFile v0.20260916.221748:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-09T17:56:22+00:00): [Publishing prevention: authoritative calendar validation and stale-preview release guard](https://github.com/usdimpact/usd-impact-site/issues/558)\n- github-issues (2026-09-15T19:21:42+00:00): [WebUI: continuous performance and stability study with real-Gateway evidence](https://github.com/openclaw/openclaw/issues/149361)\n- hacker-news-ask-hn (2026-09-16T14:59:56+00:00): [LLM based CI pipeline code generator for DSCI](https://news.ycombinator.com/item?id=49728085)\n- hacker-news-search (2026-09-05T18:38:11+00:00): [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues (2026-09-16T21:01:05+00:00): [[Admin] Reproduce duty-period management screens](https://github.com/Osiris-Balonga/wanzila/issues/49)\n- github-issues (2026-09-16T22:00:42+00:00): [Expose live Jupyter cell outputs through read-notebook](https://github.com/luke-m-selway/vscode-live-bridge/issues/5)\n- segmentfault-search (2026-09-16T22:18:15.190336+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-16T22:18:15.190336+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-16T22:18:15.190336+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-16T22:18:15.190336+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-16T22:18:15.190839+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n- segmentfault-search (2026-09-16T22:18:15.190839+00:00): [Android自动化测试一 UiAutomator官方介绍](https://segmentfault.com/a/1190000045114982)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260916.221748:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Publishing prevention: authoritative calendar validation and stale-preview release guard](https://github.com/usdimpact/usd-impact-site/issues/558)\n- github-issues：[WebUI: continuous performance and stability study with real-Gateway evidence](https://github.com/openclaw/openclaw/issues/149361)\n- hacker-news-ask-hn：[LLM based CI pipeline code generator for DSCI](https://news.ycombinator.com/item?id=49728085)\n- hacker-news-search：[User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues：[[Admin] Reproduce duty-period management screens](https://github.com/Osiris-Balonga/wanzila/issues/49)\n- github-issues：[Expose live Jupyter cell outputs through read-notebook](https://github.com/luke-m-selway/vscode-live-bridge/issues/5)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n- segmentfault-search：[Android自动化测试一 UiAutomator官方介绍](https://segmentfault.com/a/1190000045114982)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260916.221748:skill-card.md\n\n## Description:\n\nHelps software maintainers, QA engineers, open-source contributors, and product teams add useful unit tests and raise test coverage for existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, maintainers, QA engineers, open-source contributors, and product teams use this skill to plan or implement repeatable unit-test and coverage-improvement work for existing codebases. It helps turn a testing goal into scoped steps, checklists, code changes, and verification notes.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger language may activate the skill for general testing or quality requests beyond unit-test coverage work.\n\nMitigation: Use narrower trigger language for deployments that should route only explicit unit-test, coverage, or regression-test requests to this skill.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [Unit Test Coverage Helper on ClawHub](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code blocks and command snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include tailored workflows, checklists, implementation changes, verification commands, and follow-up risks.]\n\n## Skill Version(s):\n\n0.20260916.221748 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260916.221748:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260916.221748:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260911.40430: 8 files, 10538 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3276b), README.zh-CN.md (3284b), references/requirement-plan.md (5139b), skill-card.md (1902b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nFile v0.20260911.40430:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260911.40430:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [[Question] Audio Output Policy & Speech-Flow Voice Bridge Configuration](https://github.com/holman57/Adrastea/issues/6)\n- github-issues: [fix(calendar): require reviewed destinations during account replacement](https://github.com/elizaOS/eliza/issues/30991)\n- github-issues: [check: native constraint emission overwrites reviewed per-board pad-hole spacing](https://github.com/rjwalters/kicad-tools/issues/5006)\n- github-issues: [Add scriptable manufacturing-readiness runner producing hash-bound gallery evidence](https://github.com/rjwalters/kicad-tools/issues/4977)\n- hacker-news-search: [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues: [Give the observation ledger a commit path, so a parent's appends reach main through a pull request](https://github.com/joshuafolkken/kit/issues/1756)\n- github-issues: [P0: Converge Tony workstation bootstrap, Codex hygiene, skills, utilities, and Drive distribution v2](https://github.com/pinklon/engineering-workstation-bootstrap/issues/7)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260911.40430:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260911.40430\",\n  \"publishedAt\": 1789099643926\n}\n\nFile v0.20260911.40430:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-07T19:21:05+00:00): [[Question] Audio Output Policy & Speech-Flow Voice Bridge Configuration](https://github.com/holman57/Adrastea/issues/6)\n- github-issues (2026-09-10T07:54:29+00:00): [fix(calendar): require reviewed destinations during account replacement](https://github.com/elizaOS/eliza/issues/30991)\n- github-issues (2026-09-10T07:10:32+00:00): [check: native constraint emission overwrites reviewed per-board pad-hole spacing](https://github.com/rjwalters/kicad-tools/issues/5006)\n- github-issues (2026-09-10T05:43:59+00:00): [Add scriptable manufacturing-readiness runner producing hash-bound gallery evidence](https://github.com/rjwalters/kicad-tools/issues/4977)\n- hacker-news-search (2026-09-05T18:38:11+00:00): [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues (2026-09-11T01:10:54+00:00): [Give the observation ledger a commit path, so a parent's appends reach main through a pull request](https://github.com/joshuafolkken/kit/issues/1756)\n- github-issues (2026-09-11T03:37:04+00:00): [P0: Converge Tony workstation bootstrap, Codex hygiene, skills, utilities, and Drive distribution v2](https://github.com/pinklon/engineering-workstation-bootstrap/issues/7)\n- segmentfault-search (2026-09-11T04:05:32.568174+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-11T04:05:32.568174+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-11T04:05:32.568174+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-11T04:05:32.568863+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-11T04:05:32.568863+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260911.40430:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[[Question] Audio Output Policy & Speech-Flow Voice Bridge Configuration](https://github.com/holman57/Adrastea/issues/6)\n- github-issues：[fix(calendar): require reviewed destinations during account replacement](https://github.com/elizaOS/eliza/issues/30991)\n- github-issues：[check: native constraint emission overwrites reviewed per-board pad-hole spacing](https://github.com/rjwalters/kicad-tools/issues/5006)\n- github-issues：[Add scriptable manufacturing-readiness runner producing hash-bound gallery evidence](https://github.com/rjwalters/kicad-tools/issues/4977)\n- hacker-news-search：[User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues：[Give the observation ledger a commit path, so a parent's appends reach main through a pull request](https://github.com/joshuafolkken/kit/issues/1756)\n- github-issues：[P0: Converge Tony workstation bootstrap, Codex hygiene, skills, utilities, and Drive distribution v2](https://github.com/pinklon/engineering-workstation-bootstrap/issues/7)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260911.40430:skill-card.md\n\n## Description:\n\nHelps agents plan, implement, and verify useful unit tests and coverage improvements for existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, software maintainers, QA engineers, open-source contributors, and product teams use this skill to add practical unit tests, raise coverage, and verify that code changes do not break existing behavior.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger wording may activate the skill on general testing or software-quality requests where a narrower helper was intended.\n\nMitigation: Use explicit invocation or narrow trigger terms when maintaining the skill.\n\nRisk: Suggested code changes or test commands may be incorrect for a specific repository.\n\nMitigation: Review proposed changes and run the relevant test or verification commands before relying on the output.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n- [Requirement plan](artifact/references/requirement-plan.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, code, shell commands, configuration]\n\n**Output Format:** [Markdown with checklists, implementation guidance, code snippets, and verification commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May produce tailored test plans, reusable workflows, assumptions, limits, and verification notes.]\n\n## Skill Version(s):\n\n0.20260911.40430 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260911.40430:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260911.40430:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260908.51704: 8 files, 10879 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3271b), README.zh-CN.md (3279b), references/requirement-plan.md (5134b), skill-card.md (2324b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nFile v0.20260908.51704:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260908.51704:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [ORG-002 — Build local Commander Runner](https://github.com/haitao5867gg-cpu/LandlordEasy/issues/17)\n- github-issues: [[Exploratory] Profile - Invite the secondary contact appear as grey member in Workspace](https://github.com/Expensify/App/issues/99823)\n- github-issues: [perf(pipeline): stop re-running the full verify suite at every stage -- targeted tests while iterating, CI as the oracle for QA](https://github.com/benmarte/talos/issues/195)\n- hacker-news-search: [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- hacker-news-search: [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues: [Placement cues: drop the active-word tint in the editor and all block/word cues in the preview; preview clicks must not scroll](https://github.com/jorgeper/marky-mark/issues/345)\n- github-issues: [fix(canvas): remove permanently rendered center crosshair guides from the editor canvas](https://github.com/Cognitive-Architect/panda-stage/issues/452)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260908.51704:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260908.51704\",\n  \"publishedAt\": 1788844782212\n}\n\nFile v0.20260908.51704:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-06T13:41:38+00:00): [ORG-002 — Build local Commander Runner](https://github.com/haitao5867gg-cpu/LandlordEasy/issues/17)\n- github-issues (2026-08-29T08:46:57+00:00): [[Exploratory] Profile - Invite the secondary contact appear as grey member in Workspace](https://github.com/Expensify/App/issues/99823)\n- github-issues (2026-09-08T03:48:06+00:00): [perf(pipeline): stop re-running the full verify suite at every stage -- targeted tests while iterating, CI as the oracle for QA](https://github.com/benmarte/talos/issues/195)\n- hacker-news-search (2026-09-05T18:38:11+00:00): [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- hacker-news-search (2026-08-25T13:35:21+00:00): [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues (2026-09-07T23:45:26+00:00): [Placement cues: drop the active-word tint in the editor and all block/word cues in the preview; preview clicks must not scroll](https://github.com/jorgeper/marky-mark/issues/345)\n- github-issues (2026-09-08T05:00:00+00:00): [fix(canvas): remove permanently rendered center crosshair guides from the editor canvas](https://github.com/Cognitive-Architect/panda-stage/issues/452)\n- segmentfault-search (2026-09-08T05:17:41.291905+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-08T05:17:41.291905+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-08T05:17:41.291905+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-08T05:17:41.291905+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-08T05:17:41.292407+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260908.51704:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[ORG-002 — Build local Commander Runner](https://github.com/haitao5867gg-cpu/LandlordEasy/issues/17)\n- github-issues：[[Exploratory] Profile - Invite the secondary contact appear as grey member in Workspace](https://github.com/Expensify/App/issues/99823)\n- github-issues：[perf(pipeline): stop re-running the full verify suite at every stage -- targeted tests while iterating, CI as the oracle for QA](https://github.com/benmarte/talos/issues/195)\n- hacker-news-search：[User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- hacker-news-search：[We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues：[Placement cues: drop the active-word tint in the editor and all block/word cues in the preview; preview clicks must not scroll](https://github.com/jorgeper/marky-mark/issues/345)\n- github-issues：[fix(canvas): remove permanently rendered center crosshair guides from the editor canvas](https://github.com/Cognitive-Architect/panda-stage/issues/452)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260908.51704:skill-card.md\n\n## Description:\n\nHelps agents plan, implement, and verify useful unit tests and coverage improvements for existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, software maintainers, QA engineers, open-source contributors, and product teams use this skill to create repeatable workflows for adding meaningful unit tests, raising coverage, and checking changes against regression risk.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad activation wording may cause the skill to be invoked for general testing or quality requests.\n\nMitigation: Confirm the user wants unit-test coverage planning or implementation before making broad code changes.\n\nRisk: Generated testing recommendations or edits can introduce incorrect assumptions in large or sensitive repositories.\n\nMitigation: Review proposed tests and run the repository's normal verification commands before accepting changes.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n- [GitHub issue: ORG-002 - Build local Commander Runner](https://github.com/haitao5867gg-cpu/LandlordEasy/issues/17)\n- [GitHub issue: targeted tests while iterating](https://github.com/benmarte/talos/issues/195)\n- [Hacker News: User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Code, Shell commands, Configuration]\n\n**Output Format:** [Markdown with optional code blocks and verification commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include checklists, implementation steps, assumptions, limits, and follow-up risks.]\n\n## Skill Version(s):\n\n0.20260908.51704 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260908.51704:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260908.51704:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260907.40414: 8 files, 10383 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3088b), README.zh-CN.md (3096b), references/requirement-plan.md (4951b), skill-card.md (2063b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nFile v0.20260907.40414:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260907.40414:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [[S40] J-04: Admit the developer-live Provider Processing scope and run the baseline analysis live](https://github.com/zhouy1017/ai7-harness/issues/272)\n- hacker-news-ask-hn: [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues: [[PR Feedback] Test Suite (test_metrics_bootstrap_resolution.py)](https://github.com/tinkermonkey/codetoreum/issues/1038)\n- hacker-news-search: [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues: [Implement HGraph Build Memory Estimation](https://github.com/antgroup/vsag/issues/2865)\n- github-issues: [Add a LangChain VectorStore Adapter for pyvsag](https://github.com/antgroup/vsag/issues/2871)\n- github-issues: [Implement Balanced K-Means Clustering for IVF Partitioning](https://github.com/antgroup/vsag/issues/2870)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260907.40414:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260907.40414\",\n  \"publishedAt\": 1788753993892\n}\n\nFile v0.20260907.40414:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-06T12:18:58+00:00): [[S40] J-04: Admit the developer-live Provider Processing scope and run the baseline analysis live](https://github.com/zhouy1017/ai7-harness/issues/272)\n- hacker-news-ask-hn (2026-09-05T18:38:11+00:00): [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues (2026-09-07T03:37:10+00:00): [[PR Feedback] Test Suite (test_metrics_bootstrap_resolution.py)](https://github.com/tinkermonkey/codetoreum/issues/1038)\n- hacker-news-search (2026-08-25T13:35:21+00:00): [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues (2026-09-07T03:13:08+00:00): [Implement HGraph Build Memory Estimation](https://github.com/antgroup/vsag/issues/2865)\n- github-issues (2026-09-07T03:40:14+00:00): [Add a LangChain VectorStore Adapter for pyvsag](https://github.com/antgroup/vsag/issues/2871)\n- github-issues (2026-09-07T03:35:58+00:00): [Implement Balanced K-Means Clustering for IVF Partitioning](https://github.com/antgroup/vsag/issues/2870)\n- segmentfault-search (2026-09-07T04:05:01.356877+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-07T04:05:01.356877+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-07T04:05:01.356877+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-07T04:05:01.357379+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-07T04:05:01.357379+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260907.40414:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[[S40] J-04: Admit the developer-live Provider Processing scope and run the baseline analysis live](https://github.com/zhouy1017/ai7-harness/issues/272)\n- hacker-news-ask-hn：[User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues：[[PR Feedback] Test Suite (test_metrics_bootstrap_resolution.py)](https://github.com/tinkermonkey/codetoreum/issues/1038)\n- hacker-news-search：[We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- github-issues：[Implement HGraph Build Memory Estimation](https://github.com/antgroup/vsag/issues/2865)\n- github-issues：[Add a LangChain VectorStore Adapter for pyvsag](https://github.com/antgroup/vsag/issues/2871)\n- github-issues：[Implement Balanced K-Means Clustering for IVF Partitioning](https://github.com/antgroup/vsag/issues/2870)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260907.40414:skill-card.md\n\n## Description:\n\nHelps agents produce practical unit-test and coverage support for existing codebases, including workflows, checklists, analysis, code changes, and verification notes.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, software maintainers, QA engineers, open-source contributors, and product teams use this skill to plan, add, review, and verify unit tests and coverage improvements for existing codebases.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may activate on broad testing, regression, quality, or coverage requests because implicit invocation is enabled and trigger keywords are loose.\n\nMitigation: Confirm the user wants unit-test or coverage assistance before making code changes or recommending project-specific commands.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n- [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- [PR Feedback Test Suite](https://github.com/tinkermonkey/codetoreum/issues/1038)\n- [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code blocks and shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, implementation steps, verification commands, remaining risks, and follow-up work.]\n\n## Skill Version(s):\n\n0.20260907.40414 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260907.40414:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260907.40414:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260906.40422: 8 files, 10958 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3217b), README.zh-CN.md (3225b), references/requirement-plan.md (5080b), skill-card.md (2640b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nFile v0.20260906.40422:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260906.40422:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [[SIA][W02] Establish collector, clock, metric and capability architecture](https://github.com/davecrawley/sia/issues/14)\n- github-issues: [[Relationships][Friend][FFR-06] Prove real Mac↔Windows Friend walk on current exact source](https://github.com/vgong24/VexLife/issues/379)\n- github-issues: [MASTER: Web Pilot capability-gap and production-readiness program](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/9)\n- github-issues: [P0: Harden Streamable HTTP against DNS rebinding, hostile origins, request abuse, and unsafe exposure](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/43)\n- hacker-news-ask-hn: [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues: [Add agy (Antigravity CLI) as a third TuvalAiAgent backend, Pi-shaped and kernel-tool-free](https://github.com/kamp-us/phoenix/issues/8162)\n- hacker-news-search: [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260906.40422:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260906.40422\",\n  \"publishedAt\": 1788667622427\n}\n\nFile v0.20260906.40422:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-02T17:25:20+00:00): [[SIA][W02] Establish collector, clock, metric and capability architecture](https://github.com/davecrawley/sia/issues/14)\n- github-issues (2026-09-03T00:20:39+00:00): [[Relationships][Friend][FFR-06] Prove real Mac↔Windows Friend walk on current exact source](https://github.com/vgong24/VexLife/issues/379)\n- github-issues (2026-09-02T03:08:11+00:00): [MASTER: Web Pilot capability-gap and production-readiness program](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/9)\n- github-issues (2026-09-02T03:20:26+00:00): [P0: Harden Streamable HTTP against DNS rebinding, hostile origins, request abuse, and unsafe exposure](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/43)\n- hacker-news-ask-hn (2026-09-05T18:38:11+00:00): [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues (2026-09-06T03:41:25+00:00): [Add agy (Antigravity CLI) as a third TuvalAiAgent backend, Pi-shaped and kernel-tool-free](https://github.com/kamp-us/phoenix/issues/8162)\n- hacker-news-search (2026-08-25T13:35:21+00:00): [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search (2026-09-06T04:05:05.176721+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-06T04:05:05.176721+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-06T04:05:05.176721+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-06T04:05:05.176721+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-06T04:05:05.176721+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260906.40422:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[[SIA][W02] Establish collector, clock, metric and capability architecture](https://github.com/davecrawley/sia/issues/14)\n- github-issues：[[Relationships][Friend][FFR-06] Prove real Mac↔Windows Friend walk on current exact source](https://github.com/vgong24/VexLife/issues/379)\n- github-issues：[MASTER: Web Pilot capability-gap and production-readiness program](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/9)\n- github-issues：[P0: Harden Streamable HTTP against DNS rebinding, hostile origins, request abuse, and unsafe exposure](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/43)\n- hacker-news-ask-hn：[User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- github-issues：[Add agy (Antigravity CLI) as a third TuvalAiAgent backend, Pi-shaped and kernel-tool-free](https://github.com/kamp-us/phoenix/issues/8162)\n- hacker-news-search：[We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260906.40422:skill-card.md\n\n## Description:\n\nHelps software maintainers, QA engineers, open-source contributors, and product teams add useful unit tests and raise coverage for existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, software maintainers, QA engineers, open-source contributors, and product teams use this skill to plan, implement, and verify unit tests that protect existing behavior and improve coverage.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may activate on broad testing or quality-related requests and propose edits to a codebase.\n\nMitigation: Review the invocation context and inspect proposed test or coverage changes before applying them.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n- [[SIA][W02] Establish collector, clock, metric and capability architecture](https://github.com/davecrawley/sia/issues/14)\n- [[Relationships][Friend][FFR-06] Prove real Mac-Windows Friend walk on current exact source](https://github.com/vgong24/VexLife/issues/379)\n- [MASTER: Web Pilot capability-gap and production-readiness program](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/9)\n- [P0: Harden Streamable HTTP against DNS rebinding, hostile origins, request abuse, and unsafe exposure](https://github.com/ORCHORDS/OrchordsBrowserPilot/issues/43)\n- [User-guide-driven development with coding agents](https://news.ycombinator.com/item?id=49579372)\n- [Add agy as a third TuvalAiAgent backend](https://github.com/kamp-us/phoenix/issues/8162)\n- [We had a unit test once which only failed on Sundays](https://qntm.org/unit)\n- [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code blocks, shell commands, checklists, and implementation notes]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation commands, remaining risks, and follow-up work when useful.]\n\n## Skill Version(s):\n\n0.20260906.40422 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260906.40422:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260906.40422:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260905.61641: 8 files, 10496 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3381b), README.zh-CN.md (3389b), references/requirement-plan.md (5244b), skill-card.md (1764b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nFile v0.20260905.61641:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260905.61641:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [goobers doctor --k8s: add the six checks a real multi-node deployment needed and every existing gate missed (pin agreement, image contract, runner capacity vs allocatable, apiserver ipBlock drift, per-container pod health, OTLP signal set)](https://github.com/Agent-Clubhouse/Goobers/issues/4290)\n- github-issues: [Pre-Build Diff-Size and Iteration-Velocity Anomaly Warning in Pipeline Vitals](https://github.com/sethdford/shipwright/issues/3313)\n- github-issues: [Pre-Build Static Lint Gate for Bash 3.2 Compatibility Violations](https://github.com/sethdford/shipwright/issues/3239)\n- github-issues: [Adaptive Build-Loop Iteration Budget Based on Historical Issue Complexity](https://github.com/sethdford/shipwright/issues/3347)\n- github-issues: [Split sw-daemon.sh into scripts/lib/daemon-*.sh Modules Beyond Existing Extraction](https://github.com/sethdford/shipwright/issues/3346)\n- github-issues: [Distinguish transient/infra errors from code errors in build-loop failure classification](https://github.com/sethdford/shipwright/issues/3458)\n- hacker-news-search: [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260905.61641:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260905.61641\",\n  \"publishedAt\": 1788589165645\n}\n\nFile v0.20260905.61641:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-04T10:45:09+00:00): [goobers doctor --k8s: add the six checks a real multi-node deployment needed and every existing gate missed (pin agreement, image contract, runner capacity vs allocatable, apiserver ipBlock drift, per-container pod health, OTLP signal set)](https://github.com/Agent-Clubhouse/Goobers/issues/4290)\n- github-issues (2026-08-28T21:56:58+00:00): [Pre-Build Diff-Size and Iteration-Velocity Anomaly Warning in Pipeline Vitals](https://github.com/sethdford/shipwright/issues/3313)\n- github-issues (2026-08-28T16:02:35+00:00): [Pre-Build Static Lint Gate for Bash 3.2 Compatibility Violations](https://github.com/sethdford/shipwright/issues/3239)\n- github-issues (2026-08-29T00:12:53+00:00): [Adaptive Build-Loop Iteration Budget Based on Historical Issue Complexity](https://github.com/sethdford/shipwright/issues/3347)\n- github-issues (2026-08-29T00:12:49+00:00): [Split sw-daemon.sh into scripts/lib/daemon-*.sh Modules Beyond Existing Extraction](https://github.com/sethdford/shipwright/issues/3346)\n- github-issues (2026-08-29T08:06:28+00:00): [Distinguish transient/infra errors from code errors in build-loop failure classification](https://github.com/sethdford/shipwright/issues/3458)\n- hacker-news-search (2026-08-25T13:35:21+00:00): [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search (2026-09-05T06:17:09.256954+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-05T06:17:09.256954+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-05T06:17:09.256954+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-05T06:17:09.257626+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-05T06:17:09.257626+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, unit tests, test coverage, testing, regression, quality\n\nTrigger sentences:\n\n- Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n- Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\n\nFile v0.20260905.61641:README.zh-CN.md\n\n# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[goobers doctor --k8s: add the six checks a real multi-node deployment needed and every existing gate missed (pin agreement, image contract, runner capacity vs allocatable, apiserver ipBlock drift, per-container pod health, OTLP signal set)](https://github.com/Agent-Clubhouse/Goobers/issues/4290)\n- github-issues：[Pre-Build Diff-Size and Iteration-Velocity Anomaly Warning in Pipeline Vitals](https://github.com/sethdford/shipwright/issues/3313)\n- github-issues：[Pre-Build Static Lint Gate for Bash 3.2 Compatibility Violations](https://github.com/sethdford/shipwright/issues/3239)\n- github-issues：[Adaptive Build-Loop Iteration Budget Based on Historical Issue Complexity](https://github.com/sethdford/shipwright/issues/3347)\n- github-issues：[Split sw-daemon.sh into scripts/lib/daemon-*.sh Modules Beyond Existing Extraction](https://github.com/sethdford/shipwright/issues/3346)\n- github-issues：[Distinguish transient/infra errors from code errors in build-loop failure classification](https://github.com/sethdford/shipwright/issues/3458)\n- hacker-news-search：[We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260905.61641:skill-card.md\n\n## Description:\n\nHelps software maintainers, QA engineers, open-source contributors, and product teams add useful unit tests and raise test coverage for existing codebases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, maintainers, open-source contributors, and product teams use this skill to plan, implement, and verify practical unit-test coverage improvements for existing codebases.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad activation wording may route the skill into general software-quality or testing requests where a more specific workflow would fit better.\n\nMitigation: Confirm the request involves unit tests, test coverage, regression testing, or related code-quality work before applying the skill workflow.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/unit-test-coverage-helper)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code blocks and shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include checklists, implementation notes, assumptions, verification commands, and follow-up risks.]\n\n## Skill Version(s):\n\n0.20260905.61641 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260905.61641:SKILL.zh-CN.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  帮助用户处理“Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, unit tests, test coverage, testing, regression，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Unit Test Coverage Helper\n\n## 需求\n\n使用这个技能帮助以下用户群体：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n示例触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260905.61641:agents/openai.yaml\n\ninterface:\n  display_name: \"Unit Test Coverage Helper\"\n  short_description: \"Helps with Teams need repeatable help adding useful unit test...\"\n  default_prompt: \"Use $unit-test-coverage-helper to help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260904.60001: 8 files, 10020 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3010b), README.zh-CN.md (3018b), references/requirement-plan.md (4986b), skill-card.md (1923b), SKILL.md (3045b), SKILL.zh-CN.md (2902b), _meta.json (155b)\n\nFile v0.20260904.60001:SKILL.md\n\n---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 90/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 2 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\nFile v0.20260904.60001:README.md\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 90/100\n\nEvidence coverage: 12 signals across 2 source families.\n\n## Evidence\n\n- hacker-news-search: [Coding Agents killed my identity. How do you feel?](https://news.ycombinator.com/item?id=49389408)\n- hacker-news-search: [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n- segmentfault-search: [Android自动化测试一 UiAutomator官方介绍](https://segmentfault.com/a/1190000045114982)\n- segmentfault-search: [CSCI 2134](https://segmentfault.com/a/1190000041402955)\n- hacker-news-search: [The asteroid currently hitting front end web development](https://news.ycombinator.com/item?id=49559136)\n- hacker-news-search: [The asteroid currently hitting front end web development](https://news.ycombinator.com/item?id=49555992)\n- hacker-news-search: [Nobody Has Actually Built a Software Factory](https://news.ycombinator.com/item?id=49552994)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260904.60001:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.20260904.60001\",\n  \"publishedAt\": 1788501850937\n}\n\nFile v0.20260904.60001:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 90/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 2 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 2; sources: hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n- Score capped because corroborating evidence does not come from at least three different source families.\n\n## Evidence\n\n- hacker-news-search (2026-08-21T15:15:14+00:00): [Coding Agents killed my identity. How do you feel?](https://news.ycombinator.com/item?id=49389408)\n- hacker-news-search (2026-08-25T13:35:21+00:00): [We had a unit test once which only failed on Sundays (2015)](https://qntm.org/unit)\n- segmentfault-search (2026-09-04T06:00:50.531642+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-04T06:00:50.531642+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-04T06:00:50.531642+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-04T06:00:50.531642+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-04T06:00:50.531642+00:00): [Writing Great Unit Tests: Best and Worst Practices](https://segmentfault.com/a/1190000009709754)\n- segmentfault-search (2026-09-04T06:00:50.532648+00:00): [Android自动化测试一 UiAutomator官方介绍](https://segmentfault.com/a/1190000045114982)\n- segmentfault-search (2026-09-04T06:00:50.532648+00:00): [CSCI 2134](https://segmentfault.com/a/1190000041402955)\n- hacker-news-search (2026-09-04T00:53:19+00:00): [The asteroid currently hitting front end web development](https://news.ycombinator.com/item?id=49559136)\n- hacker-news-search (2026-09-03T20:01:24+00:00): [The asteroid currently hitting front end web development](https://news.ycombinator.com/item?id=49555992)\n- hacker-news-search (2026-09-03T16:47:09+00:00): [Nobody Has Actually Bu\n\nArchive v0.20260831.40551: 8 files, 10534 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3130b), README.zh-CN.md (3138b), references/requirement-plan.md (5000b), skill-card.md (1942b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)\n\nArchive v0.20260830.92238: 8 files, 10519 bytes\n\nFiles: agents/openai.yaml (350b), README.md (3020b), README.zh-CN.md (3028b), references/requirement-plan.md (4897b), skill-card.md (2454b), SKILL.md (3046b), SKILL.zh-CN.md (2903b), _meta.json (155b)","readmeExcerpt":"Skill: Unit Test Coverage Helper Owner: kyro-ma Summary: Helps with Teams need repeatable help adding useful unit test... Tags: latest:0.20260916.221748 Version history: v0.0.0-20261009-045810 | 2026-10-09T05:01:43.691Z | auto - Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Removed the skill-card.md file to streamline documentation. - No changes to core functionality; this rel","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: unit-test-coverage-helper\ndescription: >-\n  Help users with Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, unit tests, test coverage, testing, regression, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Unit Test Coverage Helper\n\n## Requirement\n\nUse this skill to help software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior with:\n\n> Validated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nExample trigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and r"},{"path":"README.md","content":"# Unit Test Coverage Helper\n\n## Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn: [Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues: [feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues: [Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues: [Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search: [Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search: [Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search: [Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues: [Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\nTrigger sentences:\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n-"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"unit-test-coverage-helper\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522103691\n}"},{"path":"references/requirement-plan.md","content":"# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nsoftware maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-10-07T11:54:36+00:00): [Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn (2026-10-07T18:11:28+00:00): [Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues (2026-10-09T03:57:56+00:00): [feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues (2026-10-08T01:19:12+00:00): [Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues (2026-10-08T20:52:07+00:00): [Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search (2026-10-03T19:16:41+00:00): [Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search (2026-10-03T11:12:24+00:00): [Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search (2026-09-26T13:48:45+00:00): [Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues (2026-10-08T11:57:24+00:00): [Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:33.802675+00:00): [typescript](https://segmentfault.com/t/typescript)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliv"},{"path":"README.zh-CN.md","content":"# Unit Test Coverage Helper\n\n## 需求\n\nValidated demand: Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：software maintainers, QA engineers, open-source contributors, and product teams who need confidence that changes do not break existing behavior\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Codex lanes A–E: close the remaining criteria (from 10-07 consolidated main)](https://github.com/MJohnsonWellabe/Tetherbound/issues/572)\n- hacker-news-ask-hn：[Ask HN: Which frontier model can do code security reviews](https://news.ycombinator.com/item?id=49996594)\n- github-issues：[feat(review-pr-staging): scope bundle review to cross-PR interactions and unreviewed commits; dedupe findings](https://github.com/RapierCraftStudios/ForgeDock/issues/3451)\n- github-issues：[Cap Node heap for api and worker from env with validated config](https://github.com/AbdelrhmanAh7/Mizano/issues/127)\n- github-issues：[Sidebar: worker status widget (online/offline from the heartbeat)](https://github.com/SBub/adw-dashboard/issues/158)\n- hacker-news-search：[Unit Tests are dead (again)](https://nerder.substack.com/p/unit-tests-are-dead-again)\n- hacker-news-search：[Developers Delete Unit Test Lines with AI Shift](https://x.com/i/trending/2106211685782483337)\n- hacker-news-search：[Unit tests mark territory more than squash bugs](https://yosefk.com/blog/unit-tests-mark-territory-more-than-squash-bugs.html)\n- github-issues：[Note gets removed](https://github.com/guettli/sharedinbox/issues/998)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `unit tests`, `test coverage`, `testing`, `regression`, `quality`\n\n触发句：\n\n- `Help me Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `I need a practical workflow for Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n- `Use $unit-test-coverage-helper to handle Teams need repeatable help adding useful unit tests and raising test coverage for existing codebases.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2091,"uniquenessScore":31,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T18:47:51.277Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:52:56.299Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}