[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H3B41BA0ZRSTM92D7ZB949":3,"skill-same:01M6H3B41BA0ZRSTM92D7ZB949":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":24,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6H3B41BA0ZRSTM92D7ZB949","react-render-delta",null,"Prove a React rendering or memoization change actually reduced work, with a delivery gate and a reported band. Covers re-render counts (why-did-you-render), selector recomputes (reselect's real `.recomputations()` API), and A\u002FB arms toggled at a FIXED commit rather than across a merge boundary. The falsifier is an arm whose treatment never reached the built bundle — a null from undelivered treatment is indistinguishable from a null from a small effect and reports as the second. Triggers on \u002Fmms-react-render-delta, or when asked to prove a component stopped over-rendering, measure selector recomputation, validate a memoization\u002FReact Compiler change, run a render-count A\u002FB, or interpret a re-render benchmark. Callable by `evidence` as its React render & selector proof engine.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-react-render-delta\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-react-render-delta\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"react","render","delta","react render delta","when","second","prove","selector","re","you","with","as","triggers","across","reports","evidence","never","effect","work","engine","api","compiler","commit","2026-11-10 10:12:30",false,"---\nname: react-render-delta\ndescription: Prove a React rendering or memoization change actually reduced work, with a delivery gate and a reported band. Covers re-render counts (why-did-you-render), selector recomputes (reselect's real `.recomputations()` API), and A\u002FB arms toggled at a FIXED commit rather than across a merge boundary. The falsifier is an arm whose treatment never reached the built bundle — a null from undelivered treatment is indistinguishable from a null from a small effect and reports as the second. Triggers on \u002Fmms-react-render-delta, or when asked to prove a component stopped over-rendering, measure selector recomputation, validate a memoization\u002FReact Compiler change, run a render-count A\u002FB, or interpret a re-render benchmark. Callable by `evidence` as its React render & selector proof engine.\nmaturity: experimental\n---\n\n# \u002Freact-render-delta\n\nA render-count number is worthless until two things are true: the **treatment reached the\nartifact the browser executes**, and the number is reported as a **band** rather than a point.\nMost of this skill is those two checks. The measurement itself is easy; the failure mode is\nreporting a difference between arms that never differed.\n\n> **Falsifier.** An arm whose manipulation cannot be observed in the built bundle. If you\n> cannot point at output that differs *in kind* between arms — a symbol present in one and\n> absent in the other, a flag line in a log — the A\u002FB is not designed yet, and any delta it\n> produces is noise with a story attached.\n\n## Method\n\n1. **Name the delivery check before building arms, and verify it emits.** State how the run\n   itself will show the arms differ, then confirm that output exists on one real build before\n   scaling to N repeats. This ordering is the whole skill. A measurement launched before the\n   instrument is proven emits a null that reads exactly like \"no effect\".\n\n2. **Derive the needle from output at the stage you will grep, not one stage upstream.**\n   Compiler and bundler output are not the same text. Worked failures, both real:\n   - React Compiler at `target: '17'` emits `react-compiler-runtime`; at `target: '19'` it\n     emits `react\u002Fcompiler-runtime`. Grepping for the wrong one returns 0 in *both* arms and\n     fails the arm that actually got the treatment.\n   - `_c(` is the form **babel** emits. Metro transforms it further — in a real 119 MB React\n     Native bundle it scored 13 hits, every one a minified vendor identifier\n     (`function _c(e,t){return e|t}`), while the true compiler output went uncounted. The form\n     that survived metro was `memo_cache_sentinel` (4681 in the treated arm vs 166 in the\n     control). Same needle, two bundlers, two different answers.\n\n   Compile one real file through the project's own config and read the output. Ten minutes\n   here saves a whole run.\n\n3. **A name is not a witness — count what only exists when the module is included.** A bare\n   module specifier appears in bundled `package.json` dependency lists whether or not the\n   module was ever pulled in; a clean control arm scored exactly 1 that way and was wrongly\n   failed. Gate on artifacts that cannot appear otherwise (a runtime sentinel, a compiled call\n   site). Keep the specifier count as a diagnostic — 3081-vs-1 is informative, it just isn't a\n   boolean.\n\n4. **Use the library's real counter before injecting your own.** `reselect` exposes\n   **`.recomputations()`** on memoized selectors — a genuine API, not a patch. Read it (sample\n   on an interval if the count should visibly climb). An injected `console.log` you added to a\n   selector body is an authored claim, not an observation; reach for it only when no real API\n   exists, and say so when you do. *(Note: the evidence catalog's render-and-selector entry long claimed there\n   was \"no built-in selector-call counter\". There is.)*\n\n5. **Toggle at a fixed commit, not across a merge boundary.** Same tree in both arms, one\n   thing different. A commit boundary drags in unrelated change you will then be unable to\n   exclude. When the real commit bundles two changes (a scope change *and* a version bump),\n   reproduce only the one under test — moving both reintroduces the confound the fixed-commit\n   design exists to remove, and can silently flip your delivery needle mid-experiment.\n\n6. **Repeat the capture, not the build; report the band.** Counts vary run to run — one\n   baseline measured 153\u002F164\u002F224 across three runs. The build dominates cost (~6 min vs ~90 s\n   per capture), so repeats are nearly free. Publish one artifact; report every repeat's count.\n\n7. **When the delta is under the spread, say \"not resolvable at this n\" and give the MDE.**\n   Not \"no effect\". State the smallest detectable effect and what n would resolve the observed\n   difference. A real worked result: 112–128 vs 115–133, delta 4.6%, t=1.33 — with delivery\n   proven (1244 compiled sites vs 0), so the null was about effect size, not plumbing.\n\n8. **A check that finds nothing needs a positive control.** Before believing a zero, confirm\n   the same check finds something it should. A search that returned \"0 references\" looked like\n   confirmation until searching for a string known to be present *also* returned 0 — the index\n   didn't reach that content and the zero meant nothing.\n\n## Gates, in order\n\n| gate | asserts | on failure |\n|---|---|---|\n| source manipulation | the intended edit applied, and *only* it | abort the arm |\n| **delivery** | the change reached the built bundle | abort **before any capture** |\n| metric | the instrument emitted a non-zero count on capture 1 | abort before spending repeats |\n\nEach catches what the previous cannot. Source changing is not delivery; delivery is not the\ninstrument working. Wire them as script-level aborts so a broken arm cannot report a number —\n\"refusing to emit a render count from an arm whose treatment is unproven\" is the correct\noutput, and it is not a failure of the run.\n\n**Never relax a gate to make an arm pass.** When a gate fires, go read the artifact and find\nthe mechanism first. Loosening is the work-reducing direction, which is exactly where scrutiny\ncollapses. Demoting a needle from gate to diagnostic *after* proving it fires for an unrelated\nreason is legitimate; doing it because the arm failed is not.\n\n## What the count does and does not mean\n\nWDYR counts **every** re-render in the measured window, including boot settling — not only the\ncascade a given fix targeted. So an RCA predicting \"→ 0 re-renders\" for a specific cascade is\nnot refuted by a non-zero WDYR total. Say which quantity you measured, and don't let a global\ncounter stand in for a scoped claim.\n\nGlobal application does not imply a large effect: 1244 auto-memoized call sites moved one\ninteraction's re-render count under 5%. Reach for a flow the change plausibly dominates, and\ntreat a single flow as a lower bound on reach, not a summary of it.\n\n## Caveats to publish with the number\n\nFixture parity (structurally matched vs byte-identical), arm ordering (randomized or not),\nwhat window the counter covers, and how many flows were measured. State them; they are cheap\nand their absence is what makes a number unfalsifiable.\n\n## Related\n\n- `evidence` — packages this skill's output as its [React render & selector proof category](https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fpr-workflow\u002Fskills\u002Fevidence\u002Freferences\u002Fevidence-catalog.md).\n- `memory-leak`, `supply-chain-audit` — sibling engines behind other categories.\n","# \u002Freact-render-delta\n\nA render-count number is worthless until two things are true: the **treatment reached the\nartifact the browser executes**, and the number is reported as a **band** rather than a point.\nMost of this skill is those two checks. The measurement itself is easy; the failure mode is\nreporting a difference between arms that never differed.\n\n> **Falsifier.** An arm whose manipulation cannot be observed in the built bundle. If you\n> cannot point at output that differs *in kind* between arms — a symbol present in one and\n> absent in the other, a flag line in a log — the A\u002FB is not designed yet, and any delta it\n> produces is noise with a story attached.\n\n## Method\n\n1. **Name the delivery check before building arms, and verify it emits.** State how the run\n   itself will show the arms differ, then confirm that output exists on one real build before\n   scaling to N repeats. This ordering is the whole skill. A measurement launched before the\n   instrument is proven emits a null that reads exactly like \"no effect\".\n\n2. **Derive the needle from output at the stage you will grep, not one stage upstream.**\n   Compiler and bundler output are not the same text. Worked failures, both real:\n   - React Compiler at `target: '17'` emits `react-compiler-runtime`; at `target: '19'` it\n     emits `react\u002Fcompiler-runtime`. Grepping for the wrong one returns 0 in *both* arms and\n     fails the arm that actually got the treatment.\n   - `_c(` is the form **babel** emits. Metro transforms it further — in a real 119 MB React\n     Native bundle it scored 13 hits, every one a minified vendor identifier\n     (`function _c(e,t){return e|t}`), while the true compiler output went uncounted. The form\n     that survived metro was `memo_cache_sentinel` (4681 in the treated arm vs 166 in the\n     control). Same needle, two bundlers, two different answers.\n\n   Compile one real file through the project's own config and read the output. Ten minutes\n   here saves a whole run.\n\n3. **A name is not a witness — count what only exists when the module is included.** A bare\n   module specifier appears in bundled `package.json` dependency lists whether or not the\n   module was ever pulled in; a clean control arm scored exactly 1 that way and was wrongly\n   failed. Gate on artifacts that cannot appear otherwise (a runtime sentinel, a compiled call\n   site). Keep the specifier count as a diagnostic — 3081-vs-1 is informative, it just isn't a\n   boolean.\n\n4. **Use the library's real counter before injecting your own.** `reselect` exposes\n   **`.recomputations()`** on memoized selectors — a genuine API, not a patch. Read it (sample\n   on an interval if the count should visibly climb). An injected `console.log` you added to a\n   selector body is an authored claim, not an observation; reach for it only when no real API\n   exists, and say so when you do. *(Note: the evidence catalog's render-and-selector entry long claimed there\n   was \"no built-in selector-call counter\". There is.)*\n\n5. **Toggle at a fixed commit, not across a merge boundary.** Same tree in both arms, one\n   thing different. A commit boundary drags in unrelated change you will then be unable to\n   exclude. When the real commit bundles two changes (a scope change *and* a version bump),\n   reproduce only the one under test — moving both reintroduces the confound the fixed-commit\n   design exists to remove, and can silently flip your delivery needle mid-experiment.\n\n6. **Repeat the capture, not the build; report the band.** Counts vary run to run — one\n   baseline measured 153\u002F164\u002F224 across three runs. The build dominates cost (~6 min vs ~90 s\n   per capture), so repeats are nearly free. Publish one artifact; report every repeat's count.\n\n7. **When the delta is under the spread, say \"not resolvable at this n\" and give the MDE.**\n   Not \"no effect\". State the smallest detectable effect and what n would resolve the observed\n   difference. A real worked result: 112–128 vs 115–133, delta 4.6%, t=1.33 — with delivery\n   proven (1244 compiled sites vs 0), so the null was about effect size, not plumbing.\n\n8. **A check that finds nothing needs a positive control.** Before believing a zero, confirm\n   the same check finds something it should. A search that returned \"0 references\" looked like\n   confirmation until searching for a string known to be present *also* returned 0 — the index\n   didn't reach that content and the zero meant nothing.\n\n## Gates, in order\n\n| gate | asserts | on failure |\n|---|---|---|\n| source manipulation | the intended edit applied, and *only* it | abort the arm |\n| **delivery** | the change reached the built bundle | abort **before any capture** |\n| metric | the instrument emitted a non-zero count on capture 1 | abort before spending repeats |\n\nEach catches what the previous cannot. Source changing is not delivery; delivery is not the\ninstrument working. Wire them as script-level aborts so a broken arm cannot report a number —\n\"refusing to emit a render count from an arm whose treatment is unproven\" is the correct\noutput, and it is not a failure of the run.\n\n**Never relax a gate to make an arm pass.** When a gate fires, go read the artifact and find\nthe mechanism first. Loosening is the work-reducing direction, which is exactly where scrutiny\ncollapses. Demoting a needle from gate to diagnostic *after* proving it fires for an unrelated\nreason is legitimate; doing it because the arm failed is not.\n\n## What the count does and does not mean\n\nWDYR counts **every** re-render in the measured window, including boot settling — not only the\ncascade a given fix targeted. So an RCA predicting \"→ 0 re-renders\" for a specific cascade is\nnot refuted by a non-zero WDYR total. Say which quantity you measured, and don't let a global\ncounter stand in for a scoped claim.\n\nGlobal application does not imply a large effect: 1244 auto-memoized call sites moved one\ninteraction's re-render count under 5%. Reach for a flow the change plausibly dominates, and\ntreat a single flow as a lower bound on reach, not a summary of it.\n\n## Caveats to publish with the number\n\nFixture parity (structurally matched vs byte-identical), arm ordering (randomized or not),\nwhat window the counter covers, and how many flows were measured. State them; they are cheap\nand their absence is what makes a number unfalsifiable.\n\n## Related\n\n- `evidence` — packages this skill's output as its [React render & selector proof category](https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fpr-workflow\u002Fskills\u002Fevidence\u002Freferences\u002Fevidence-catalog.md).\n- `memory-leak`, `supply-chain-audit` — sibling engines behind other categories.\n",{"name":5,"maturity":53,"description":7},"experimental","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fwallets\u002Fmetamask-official-react-render-delta",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-14 02:27:51",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill react-render-delta",{"tool":69,"command":70},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill react-render-delta",{"tool":72,"command":73},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill react-render-delta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-react-render-delta\u002FSKILL.md",true,[77,81,87],{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",1065,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"SOURCE.md","REFERENCE","参考文档",373,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-react-render-delta\u002FSOURCE.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-react-render-delta\u002FTRUST.auto.yaml",[92,119,141,159,172,182],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":48},"01M712C436EQYE43342Q4E7GG1","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,25,114,115,116,117,118],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","browser","layout","screen","network","metamask",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":48},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[128,129,130,45,131,132,133,134,135,136,137,138,139,140],"mexc spot websocket","spot","websocket","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":48},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[149,129,150,151,152,153,154,138,137,136,155,156,157,132,158,131,45],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":48},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[167,168,130,169,170,139,137,171,135,134,132,131],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":173,"name":174,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":48},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[179,180,181],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":48},"01M6H0Z28Q3R8J0S799GJQWXM3","verify-tests-cover-changed-lines","Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[190,191,192,193,194,195,196,197,198,199,200],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","use","patch","code","share"]