[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3GHAHDQ08PR247BEXDK9B":3,"skill-same:01M7B3GHAHDQ08PR247BEXDK9B":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7B3GHAHDQ08PR247BEXDK9B","debugging-systematically",null,"Use when a test fails, a bug is reported, or observed behavior does not match expectation, and before proposing or applying any fix.","vadimvitvickiy\u002Fvv-agent-kit","vadimvitvickiy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5019512?v=4","01M7B3ABRYF7KHBCDW6GB2XH0C","Vadim Vitvitskii","01M7B3ABSZYG9MXP1CC7BQYM25",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdebugging-systematically\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: debugging-systematically\ndescription: Use when a test fails, a bug is reported, or observed behavior does not match expectation, and before proposing or applying any fix.\n---\n\n# Debugging systematically\n\n**A fix you cannot explain is a coincidence.** If you cannot name the line that produced the wrong\nvalue and why, do not change anything. This skill owns *do I know why*; `vvkit:verifying-changes`\nowns *did I run it*.\n\n## Reproduce before theorizing\n\n- Get a deterministic reproduction at the smallest scope that still fails — one test, one input, one\n  path.\n- **Intermittency is the finding.** Once in twenty is almost always ordering, timing or shared state.\n  Record the rate before changing anything; it is how you will know a fix worked.\n- A reproduction that resists shrinking: shrink the environment — fewer threads, a fixed seed, one\n  device, one item.\n\n## Trace to where it originates\n\n- Walk the wrong value back to where correct input first became wrong output — not where it was\n  observed. The fix belongs in the gap.\n- Ask **which layer should have rejected this?** A nil crashing a view was allowed by the model\n  builder, the parser, and a schema that made the field optional. The defect is where the invariant\n  should have held.\n- Fix it there, so the class of bug becomes unrepresentable rather than this instance survivable.\n- A toolchain failure no change explains: read the **last** error in the log, and rule out an\n  exhausted resource first. A full disk surfaces as a corrupt cache or a linker failure.\n\n## Instrument every boundary the path crosses\n\n- Across components, each layer looks correct on its own. Log what enters and leaves each boundary,\n  run once; the first with right input and wrong output names the component.\n- Configuration too: a variable set in the workflow and absent in the script it launches looks like a\n  logic bug from inside.\n\n## One hypothesis, one change\n\n- State it as \"X is wrong because Y\"; make the smallest change that would falsify it.\n- Two changes in one run cannot be attributed, and the useless one stays as a false fix.\n- Revert a failed hypothesis's change before forming the next.\n\n## A live incident mitigates first\n\n- Production failing now: stop the harm — roll back, flip the flag, shed traffic — as an open\n  decision, undone once the cause is fixed.\n- First keep the evidence — logs, a failing request, the bad record — since a rollback erases the\n  reproduction. Label the change as mitigation, then debug against that evidence.\n\n## Band-aids are never the fix\n\n| Band-aid | What it costs later |\n|-|-|\n| A flag that disables the failing path | The path stays broken with two behaviors to reason about; the flag outlives everyone who knew why |\n| A special case for the input that failed | The next input in the class fails the same way, and the pattern that names the cause is hidden |\n| A guard that swallows the bad state | A crash with a stack trace becomes silently wrong data, further from the cause |\n| A sleep or retry over a race | The race now depends on machine speed and returns on faster CI or under load, reading as deliberate |\n| Widening a type to accept what broke it | The invariant is deleted instead of enforced; every reader inherits the doubt |\n\nBlocked and must ship a workaround: **say it is one, and state the real cause.** An unlabelled\nband-aid is never revisited.\n\n## Two failed fixes on one premise\n\n- **Two fixes resting on the same assumption fail the same way:** write that premise in one sentence\n  and test it before a third fix.\n- **Three failed fixes is a design finding.** When each exposes coupling somewhere new, the structure\n  is wrong; a fourth fix is sunk cost. Take what the attempts revealed and the structural question to\n  the human — restructuring is their decision.\n- The human's questions are signals: \"is that not happening?\" — you assumed; \"will it show us…?\" —\n  evidence was due first; \"stop guessing\" — fixes without a cause. Go back to reproducing.\n\n## When the cause is outside the code\n\nTiming on shared infrastructure, an external service, a platform defect: write down what was\ninvestigated, add handling that fails visibly — a bounded, logged retry, a timeout, a clear error —\nand logging that catches it next time. Suspect this conclusion: most \"no root cause\" is an\ninvestigation stopped early.\n\n## After the fix, harden the path\n\nMake the bad value unreachable: reject it at the entry point, check it where the operation depends on\nit, refuse the dangerous operation where it must never run — such as a test touching a real\ndirectory. Each fails loudly; a guard that swallows is the band-aid above.\n\n## Bisect when the trace goes cold\n\n- Bisect the history, the input or the configuration.\n- Automate the predicate — a script exiting 0 for good, 1 for bad. Eyeballing misclassifies silently.\n- **Bisect names the commit that exposed a defect, not always the one that introduced it.** Treat it\n  as where to read, not the answer.\n- For input, halve the dataset until one record fails alone.\n\n## Before you fix\n\n- [ ] The failure reproduces on demand, and you know the rate if it is intermittent\n- [ ] You can name the line that produced the wrong value, not just where it surfaced\n- [ ] You can name the layer that should have rejected it\n- [ ] You can say what the fix breaks if your explanation is wrong\n- [ ] A test fails for this reason now and passes after — see `vvkit:writing-tests`\n","# Debugging systematically\n\n**A fix you cannot explain is a coincidence.** If you cannot name the line that produced the wrong\nvalue and why, do not change anything. This skill owns *do I know why*; `vvkit:verifying-changes`\nowns *did I run it*.\n\n## Reproduce before theorizing\n\n- Get a deterministic reproduction at the smallest scope that still fails — one test, one input, one\n  path.\n- **Intermittency is the finding.** Once in twenty is almost always ordering, timing or shared state.\n  Record the rate before changing anything; it is how you will know a fix worked.\n- A reproduction that resists shrinking: shrink the environment — fewer threads, a fixed seed, one\n  device, one item.\n\n## Trace to where it originates\n\n- Walk the wrong value back to where correct input first became wrong output — not where it was\n  observed. The fix belongs in the gap.\n- Ask **which layer should have rejected this?** A nil crashing a view was allowed by the model\n  builder, the parser, and a schema that made the field optional. The defect is where the invariant\n  should have held.\n- Fix it there, so the class of bug becomes unrepresentable rather than this instance survivable.\n- A toolchain failure no change explains: read the **last** error in the log, and rule out an\n  exhausted resource first. A full disk surfaces as a corrupt cache or a linker failure.\n\n## Instrument every boundary the path crosses\n\n- Across components, each layer looks correct on its own. Log what enters and leaves each boundary,\n  run once; the first with right input and wrong output names the component.\n- Configuration too: a variable set in the workflow and absent in the script it launches looks like a\n  logic bug from inside.\n\n## One hypothesis, one change\n\n- State it as \"X is wrong because Y\"; make the smallest change that would falsify it.\n- Two changes in one run cannot be attributed, and the useless one stays as a false fix.\n- Revert a failed hypothesis's change before forming the next.\n\n## A live incident mitigates first\n\n- Production failing now: stop the harm — roll back, flip the flag, shed traffic — as an open\n  decision, undone once the cause is fixed.\n- First keep the evidence — logs, a failing request, the bad record — since a rollback erases the\n  reproduction. Label the change as mitigation, then debug against that evidence.\n\n## Band-aids are never the fix\n\n| Band-aid | What it costs later |\n|-|-|\n| A flag that disables the failing path | The path stays broken with two behaviors to reason about; the flag outlives everyone who knew why |\n| A special case for the input that failed | The next input in the class fails the same way, and the pattern that names the cause is hidden |\n| A guard that swallows the bad state | A crash with a stack trace becomes silently wrong data, further from the cause |\n| A sleep or retry over a race | The race now depends on machine speed and returns on faster CI or under load, reading as deliberate |\n| Widening a type to accept what broke it | The invariant is deleted instead of enforced; every reader inherits the doubt |\n\nBlocked and must ship a workaround: **say it is one, and state the real cause.** An unlabelled\nband-aid is never revisited.\n\n## Two failed fixes on one premise\n\n- **Two fixes resting on the same assumption fail the same way:** write that premise in one sentence\n  and test it before a third fix.\n- **Three failed fixes is a design finding.** When each exposes coupling somewhere new, the structure\n  is wrong; a fourth fix is sunk cost. Take what the attempts revealed and the structural question to\n  the human — restructuring is their decision.\n- The human's questions are signals: \"is that not happening?\" — you assumed; \"will it show us…?\" —\n  evidence was due first; \"stop guessing\" — fixes without a cause. Go back to reproducing.\n\n## When the cause is outside the code\n\nTiming on shared infrastructure, an external service, a platform defect: write down what was\ninvestigated, add handling that fails visibly — a bounded, logged retry, a timeout, a clear error —\nand logging that catches it next time. Suspect this conclusion: most \"no root cause\" is an\ninvestigation stopped early.\n\n## After the fix, harden the path\n\nMake the bad value unreachable: reject it at the entry point, check it where the operation depends on\nit, refuse the dangerous operation where it must never run — such as a test touching a real\ndirectory. Each fails loudly; a guard that swallows is the band-aid above.\n\n## Bisect when the trace goes cold\n\n- Bisect the history, the input or the configuration.\n- Automate the predicate — a script exiting 0 for good, 1 for bad. Eyeballing misclassifies silently.\n- **Bisect names the commit that exposed a defect, not always the one that introduced it.** Treat it\n  as where to read, not the answer.\n- For input, halve the dataset until one record fails alone.\n\n## Before you fix\n\n- [ ] The failure reproduces on demand, and you know the rate if it is intermittent\n- [ ] You can name the line that produced the wrong value, not just where it surfaced\n- [ ] You can name the layer that should have rejected it\n- [ ] You can say what the fix breaks if your explanation is wrong\n- [ ] A test fails for this reason now and passes after — see `vvkit:writing-tests`\n",{"name":5,"description":7},"main","cc22a222a76add5759a2df5fadf231a758691db5","skills\u002Fdebugging-systematically","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy","Senior iOS engineer. Architecture, SDKs and apps for iOS, tvOS and watchOS.","2026-11-13 19:10:29",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add vadimvitvickiy\u002Fvv-agent-kit --skill debugging-systematically",{"tool":37,"command":38},"bunx","bunx skills add vadimvitvickiy\u002Fvv-agent-kit --skill debugging-systematically",{"tool":40,"command":41},"pnpm","pnpm dlx skills add vadimvitvickiy\u002Fvv-agent-kit --skill debugging-systematically","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdebugging-systematically\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7B3JN7VG0YJ4JB8RP6HYZSJ","no-heading","Use when proving that the validator rejects a body with no H1 and a force-loading @-link.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fno-heading\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7B3JJMEW4E710ZG6HYJ7BWV","wrong-name-does-not-match-dir","Dispatches a subagent per task and reviews between each one.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fbroken-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7B3JGE9MFT1HRP41YRVKN97","writing-tests","Use when adding or changing behavior, fixing a bug, or judging whether an existing or generated test earns its place.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-tests\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7B3JD5X32VEBDBN7HB8E17Z","writing-skills","Use when authoring or editing a skill, agent, command or hook for this kit, or when deciding whether a piece of guidance belongs in a skill at all.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7B3J992MZH2QVZRED0DRPD9","writing-project-instructions","Use when creating or editing a CLAUDE.md or AGENTS.md, when it has grown long, or when a rule in it also exists in an installed skill.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-project-instructions\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7B3J55C5WPWN20QXP9ET848","writing-logs","Use when adding or reviewing log statements, or when deciding what level a message belongs at.","https:\u002F\u002Fgithub.com\u002Fvadimvitvickiy\u002Fvv-agent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-logs\u002FSKILL.md",[],[]]