[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDFQBEXQ7K3MF1N1NYZJ70":3,"skill-same:01M6PDFQBEXQ7K3MF1N1NYZJ70":75},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6PDFQBEXQ7K3MF1N1NYZJ70","diagnosing-bugs",null,"Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation. Use when something is broken, failing, throwing, intermittently wrong, or unexpectedly slow.","stevesolun\u002Fctx","stevesolun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1304538?v=4","01M6PDDJQ35XAXMPJQP8YG3P2X","Steve Solun","01M6PDDJVJ663A3CMV7XQN9XAY",593,"MIT","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdiagnosing-bugs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"diagnosing bugs","bugs","performance","diagnose","Reproducible","broken","use","evidence","instrumentation","with","Wrong","2026-11-10 10:12:30",false,"---\nname: diagnosing-bugs\ndescription: Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation. Use when something is broken, failing, throwing, intermittently wrong, or unexpectedly slow.\n---\n\n# Diagnosing Bugs\n\nStart from evidence and adapt the depth of the investigation to the problem.\nRead relevant repository context and architectural decisions when they exist.\n\n## Establish a useful signal\n\nReproduce the reported symptom with the cheapest signal that distinguishes\nbroken from fixed. A focused test or script is ideal when practical; logs,\ntraces, snapshots, comparisons, or measured timings may be better for other\nfailures. Tighten the loop by improving speed, specificity, and determinism.\n\nIf an exact reproduction is unavailable, continue with the strongest evidence\navailable and state the limitation. Request an artifact, access, or temporary\ninstrumentation only when it would materially improve the diagnosis.\n\nFor feedback-loop options and debugging tactics, load the\n[debugging playbook](references\u002Fdebugging-playbook.md) as needed. For a rare\nmanual reproduction, adapt\n[`scripts\u002Fhitl-loop.template.sh`](scripts\u002Fhitl-loop.template.sh).\n\n## Narrow and explain\n\nMinimize the reproducing scenario when doing so will shrink the search space.\nForm a small ranked set of falsifiable hypotheses from the evidence, then choose\nprobes that best distinguish them. Share hypotheses with the user when their\ndomain knowledge could redirect the investigation; do not make routine progress\ndepend on a checkpoint.\n\nUse targeted instrumentation at boundaries that separate plausible causes.\nChange as little as practical per probe. For performance regressions, establish\na baseline and use profiling, query plans, or bisection before optimizing.\n\n## Fix and verify\n\nAdd a regression test when a stable seam can represent the real failure. If it\ncannot, explain the coverage gap rather than adding a misleading test. Apply the\nsmallest justified fix, then rerun both the focused signal and relevant nearby\nchecks.\n\nRemove temporary instrumentation and artifacts unless the user wants to retain\nthem. Report the observed cause, the evidence that supports it, what was\nverified, and any remaining uncertainty. Recommend architectural follow-up only\nwhen the diagnosis exposes a concrete recurring weakness.\n","# Diagnosing Bugs\n\nStart from evidence and adapt the depth of the investigation to the problem.\nRead relevant repository context and architectural decisions when they exist.\n\n## Establish a useful signal\n\nReproduce the reported symptom with the cheapest signal that distinguishes\nbroken from fixed. A focused test or script is ideal when practical; logs,\ntraces, snapshots, comparisons, or measured timings may be better for other\nfailures. Tighten the loop by improving speed, specificity, and determinism.\n\nIf an exact reproduction is unavailable, continue with the strongest evidence\navailable and state the limitation. Request an artifact, access, or temporary\ninstrumentation only when it would materially improve the diagnosis.\n\nFor feedback-loop options and debugging tactics, load the\n[debugging playbook](references\u002Fdebugging-playbook.md) as needed. For a rare\nmanual reproduction, adapt\n[`scripts\u002Fhitl-loop.template.sh`](scripts\u002Fhitl-loop.template.sh).\n\n## Narrow and explain\n\nMinimize the reproducing scenario when doing so will shrink the search space.\nForm a small ranked set of falsifiable hypotheses from the evidence, then choose\nprobes that best distinguish them. Share hypotheses with the user when their\ndomain knowledge could redirect the investigation; do not make routine progress\ndepend on a checkpoint.\n\nUse targeted instrumentation at boundaries that separate plausible causes.\nChange as little as practical per probe. For performance regressions, establish\na baseline and use profiling, query plans, or bisection before optimizing.\n\n## Fix and verify\n\nAdd a regression test when a stable seam can represent the real failure. If it\ncannot, explain the coverage gap rather than adding a misleading test. Apply the\nsmallest justified fix, then rerun both the focused signal and relevant nearby\nchecks.\n\nRemove temporary instrumentation and artifacts unless the user wants to retain\nthem. Report the observed cause, the evidence that supports it, what was\nverified, and any remaining uncertainty. Recommend architectural follow-up only\nwhen the diagnosis exposes a concrete recurring weakness.\n",{"name":5,"description":7},"main","11b582a7cd4d549f1e83c412e04421bcc9c3fc28",".agents\u002Fskills\u002Fdiagnosing-bugs",69,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx","https:\u002F\u002Fstevesolun.github.io\u002Fctx\u002F","https:\u002F\u002Fgithub.com\u002Fstevesolun","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fsolunsteve\u002F","High motivated, dedicated, fast learner data scientist and enthusiastic researcher.","2026-10-15 03:55:28",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add stevesolun\u002Fctx --skill diagnosing-bugs",{"tool":51,"command":52},"bunx","bunx skills add stevesolun\u002Fctx --skill diagnosing-bugs",{"tool":54,"command":55},"pnpm","pnpm dlx skills add stevesolun\u002Fctx --skill diagnosing-bugs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdiagnosing-bugs\u002FSKILL.md",true,[59,65,69],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",103,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdiagnosing-bugs\u002Fagents\u002Fopenai.yaml",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fdebugging-playbook.md",2344,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdiagnosing-bugs\u002Freferences\u002Fdebugging-playbook.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fhitl-loop.template.sh","SCRIPT","脚本",1164,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdiagnosing-bugs\u002Fscripts\u002Fhitl-loop.template.sh",[76,102,126,151,177,198],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":30},"01M6PDTT7F6Z9T6G6H92845RNC","toolbox","Pre\u002Fpost dev toolbox — named bundles of skills\u002Fagents loaded before development work and councils of experts invoked after. Run \u002Ftoolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ftoolbox\u002FSKILL.md",[],[78,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"cli","development","run","start","team","work","list","initialize","export","up","activate","feature","end","new repo","false","import","experts","at","invoke",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":30},"01M6PDTNZ10BAW6VY49S40NCBB","skill-router","Alive skill router — reads the current project's stack and loads\u002Funloads skills dynamically. Invoke at session start or when project context changes.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Fskill-router\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[114,115,86,116,117,118,119,120,121,122,123,124,100,125,101],"router","skill router","Meta","stack","context","session","project context","project","loads","session start","true","changes",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":30},"01M6PDTGVDG503T4QNX64KJMAC","repo-stats-autoupdate","Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes\u002Fedges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Frepo-stats-autoupdate\u002FSKILL.md",[132],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[134,135,136,137,138,139,140,141,142,143,144,145,25,146,147,97,28,148,149,150],"stats","repo","repo stats autoupdate","test","commit","sync","release","git","graph","pre-commit","inventory","README","publishing","communities","hook","number","inline",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":163,"publishedAt":30},"01M6PDTC3AB7H4NXJFS3SDKQG9","find-skills","Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add\u002Fupdate a skill, or needs a repeatable procedure for finding candidate skills safely.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ffind-skills\u002FSKILL.md",[157,158],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[164,165,83,166,167,168,169,170,25,48,171,172,173,174,175,176],"find skills","find","update","search","api","user","catalog","discover","add","skills cli","for","candidate","ctx",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":30},"01M6PDT6ETDH54GGY7K8E29Y9V","no-mistakes","Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fno-mistakes\u002Fskills\u002Fno-mistakes\u002FSKILL.md",[],[184,185,137,186,187,188,85,189,190,191,192,193,194,195,25,196,197,94,124,125],"no mistakes","review","change","validate","pr","lint","push","ci","pipeline","ship","rebase","branch","intent","upstream",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":206,"publishedAt":30},"01M6PDT18DD3HETZF1CF39CT8J","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fmattpocock\u002Fzoom-out\u002FSKILL.md",[204,205],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},[207,208,209,210,118,25,211,212,28,213,214,124,215,216],"zoom out","zoom","code","how","it","understand","you","re","perspective","section"]