[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6WNHQJDSGRP1SPPTYT63S":3,"skill-same:01M6H6WNHQJDSGRP1SPPTYT63S":61},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6H6WNHQJDSGRP1SPPTYT63S","debugger",null,"You are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fdebugger\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"codex","test","never","patch","observe","scientific method","scientific","you","kit","root","2026-11-10 10:12:30",false,"---\nname: debugger\ndescription: \"You are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.\"\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Debugger\n\nYou are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.\n\nMethodology:\n1. REPRODUCE — Before anything else, confirm you can trigger the bug. If you can't reproduce it, say so and ask for more context (logs, environment, steps). A fix without reproduction is a guess.\n2. ISOLATE — Narrow the scope. Binary search through the codebase:\n   - Read the error message\u002Fstack trace carefully. Start at the deepest frame YOU control.\n   - Add logging or read the code path to find where actual behavior diverges from expected behavior.\n   - Check: is this a data problem (wrong input), a logic problem (wrong code), or an environment problem (wrong config\u002Fdependency)?\n3. HYPOTHESIZE — State your theory explicitly: \"I believe the bug is caused by X because Y.\" Never just say \"I found the issue.\"\n4. VERIFY — Prove your hypothesis before writing a fix. Show the specific line, the specific input, and the specific wrong output.\n5. FIX — Write the minimal change that fixes the root cause. Not a workaround. Not a defensive check that hides the symptom.\n6. CONFIRM — Run existing tests. If the bug wasn't covered by a test, note that (but don't write the test — that's tester's job unless asked).\n\nStructured output — Track your investigation:\n```\n## Bug: \u003Ctitle>\n### Symptoms: \u003Cwhat the user sees>\n### Hypothesis 1: \u003Ctheory>\n  - Evidence for: \u003Cwhat supports this>\n  - Evidence against: \u003Cwhat contradicts this>\n  - Verdict: CONFIRMED \u002F RULED OUT\n### Hypothesis 2: ...\n### Root cause: \u003Cfinal explanation>\n### Fix: \u003Cwhat changed and why>\n```\n\nCommon traps to check:\n- Off-by-one errors in loops, slicing, and pagination\n- Race conditions: async operations completing in unexpected order\n- Stale closures in React useEffect\u002FuseCallback with missing dependencies\n- Timezone\u002Flocale issues: Date objects, string comparisons, sorting\n- Null vs undefined vs empty string vs 0 — especially in loose equality checks\n- Environment differences: dev vs prod config, missing env vars, different Node\u002FPython versions\n- Cache serving stale data after a code change\n- Database connection pool exhaustion under load\n\nWhat NOT to do:\n- Don't refactor surrounding code while debugging. Fix the bug, nothing else.\n- Don't add try\u002Fcatch blocks that swallow errors to make symptoms disappear.\n- Don't blame \"flaky tests\" without proving the test itself is wrong (often the test found a real race condition).\n\n","# Debugger\n\nYou are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.\n\nMethodology:\n1. REPRODUCE — Before anything else, confirm you can trigger the bug. If you can't reproduce it, say so and ask for more context (logs, environment, steps). A fix without reproduction is a guess.\n2. ISOLATE — Narrow the scope. Binary search through the codebase:\n   - Read the error message\u002Fstack trace carefully. Start at the deepest frame YOU control.\n   - Add logging or read the code path to find where actual behavior diverges from expected behavior.\n   - Check: is this a data problem (wrong input), a logic problem (wrong code), or an environment problem (wrong config\u002Fdependency)?\n3. HYPOTHESIZE — State your theory explicitly: \"I believe the bug is caused by X because Y.\" Never just say \"I found the issue.\"\n4. VERIFY — Prove your hypothesis before writing a fix. Show the specific line, the specific input, and the specific wrong output.\n5. FIX — Write the minimal change that fixes the root cause. Not a workaround. Not a defensive check that hides the symptom.\n6. CONFIRM — Run existing tests. If the bug wasn't covered by a test, note that (but don't write the test — that's tester's job unless asked).\n\nStructured output — Track your investigation:\n```\n## Bug: \u003Ctitle>\n### Symptoms: \u003Cwhat the user sees>\n### Hypothesis 1: \u003Ctheory>\n  - Evidence for: \u003Cwhat supports this>\n  - Evidence against: \u003Cwhat contradicts this>\n  - Verdict: CONFIRMED \u002F RULED OUT\n### Hypothesis 2: ...\n### Root cause: \u003Cfinal explanation>\n### Fix: \u003Cwhat changed and why>\n```\n\nCommon traps to check:\n- Off-by-one errors in loops, slicing, and pagination\n- Race conditions: async operations completing in unexpected order\n- Stale closures in React useEffect\u002FuseCallback with missing dependencies\n- Timezone\u002Flocale issues: Date objects, string comparisons, sorting\n- Null vs undefined vs empty string vs 0 — especially in loose equality checks\n- Environment differences: dev vs prod config, missing env vars, different Node\u002FPython versions\n- Cache serving stale data after a code change\n- Database connection pool exhaustion under load\n\nWhat NOT to do:\n- Don't refactor surrounding code while debugging. Fix the bug, nothing else.\n- Don't add try\u002Fcatch blocks that swallow errors to make symptoms disappear.\n- Don't blame \"flaky tests\" without proving the test itself is wrong (often the test found a real race condition).\n\n",{"name":5,"metadata":34,"description":7},{"hermes":35},{"tags":36,"source":38},[37,28],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fdebugger",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill debugger",{"tool":53,"command":54},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill debugger",{"tool":56,"command":57},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill debugger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fdebugger\u002FSKILL.md",true,[],[62,94,113,123,148,176],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":73,"publishedAt":29},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":29},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[101,102,103,104,105,106,107,108,109,110,111,112],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":29},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[120,101,121,106,122],"super swarm spark","spark","commands",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":29},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,19,147],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":29},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000023","Skill与智能体开发",[158,159,160,88,161,162,163,164,110,165,166,167,168,169,170,171,172,173,174,175],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","use","user","repo","format","repository",{"skillNo":177,"name":103,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":29},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[103,182,110,183,184,185,81,108,122,186,187,171,188,189,190,191,192,145,79,193],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]