[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718TMHGT8MMAD72FD6FWJMY":3,"skill-same:01M718TMHGT8MMAD72FD6FWJMY":93},{"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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718TMHGT8MMAD72FD6FWJMY","oma-debug",null,"Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.","vasceannie\u002Fslopgate","vasceannie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20271133?v=4","01M718RGA8VV2EF22XJEMXVQ0Q","Travis Vasceannie","01M718RGB0GWSXBBZBN67Q6NHQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"oma debug","debug","error","regression","errors","work","diagnosis","bug","fixes","for","tests","use","specialist","root","crash","bug diagnosis","2026-11-10 10:12:30",false,"---\nname: oma-debug\ndescription: Bug diagnosis and fixing specialist - analyzes errors, identifies\n  root causes, provides fixes, and writes regression tests. Use for bug, debug,\n  error, crash, traceback, exception, and regression work.\n---\n\n# Debug Agent - Bug Fixing Specialist\n\n## Scheduling\n\n### Goal\nReproduce, diagnose, minimally fix, and regression-test bugs while preserving scope discipline and documenting root cause.\n\n### Intent signature\n- User reports a bug, crash, traceback, exception, error message, performance issue, intermittent failure, or regression.\n- User needs root cause analysis plus a minimal code fix and regression test.\n\n### When to use\n- User reports a bug with error messages\n- Something is broken and needs fixing\n- Performance issues or slowdowns\n- Intermittent failures or race conditions\n- Regression bugs\n\n### When NOT to use\n- Building new features -> use Frontend\u002FBackend\u002FMobile agents\n- General code review -> use QA Agent\n\n### Expected inputs\n- Error message, failing behavior, reproduction steps, logs, test failure, or affected code path\n- Existing tests, stack traces, environment notes, and suspected regression boundary\n\n### Expected outputs\n- Root cause explanation\n- Minimal fix scoped to the failing behavior\n- Regression test or explicit reason it cannot be added\n- Bug documentation under `.agents\u002Fresults\u002Fbugs\u002F` when appropriate\n\n### Dependencies\n- `resources\u002Fexecution-protocol.md`, examples, checklist, common patterns, and debugging checklist\n- Local codebase search and symbol\u002Freference tools\n- Project test, lint, typecheck, and runtime commands\n\n### Control-flow features\n- Branches by reproduction success, error class, suspected layer, and verification outcome\n- Reads logs\u002Fcode\u002Ftests and writes code\u002Ftests\u002Fdocs\n- Must search for similar patterns after fixing\n\n## Structural Flow\n\n### Entry\n1. Capture the reported symptom and suspected scope.\n2. Reproduce or establish the closest reliable failing signal.\n3. Identify affected files, tests, and related patterns.\n\n### Scenes\n1. **PREPARE**: Gather symptoms, logs, reproduction path, and verification command.\n2. **ACQUIRE**: Read failing code, tests, references, and similar patterns.\n3. **REASON**: Isolate root cause and reject unsupported hypotheses.\n4. **ACT**: Apply minimal fix and regression test.\n5. **VERIFY**: Re-run failing and related checks.\n6. **FINALIZE**: Document root cause, fix, test, and residual risk.\n\n### Transitions\n- If reproduction fails, use logs\u002Ftests to establish a weaker but explicit diagnostic signal.\n- If the first fix fails verification, return to root-cause analysis.\n- If similar patterns exist, inspect and patch only affected cases.\n- If the request is actually feature work, route to the relevant implementation skill.\n\n### Failure and recovery\n- If environment is missing, document the blocker and provide the closest static diagnosis.\n- If no regression test is feasible, explain why and include manual verification.\n- If fix scope grows, stop and call out the broader design issue.\n\n### Exit\n- Success: bug is fixed, regression coverage exists, and checks pass.\n- Partial success: root cause or verification blocker is explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Reproduce failure | `CALL_TOOL` | Test\u002Fruntime\u002Flog command |\n| Search affected code | `READ` | Code, tests, symbols, references |\n| Compare similar patterns | `COMPARE` | Pattern search |\n| Infer root cause | `INFER` | Diagnostic reasoning |\n| Write minimal fix | `WRITE` | Code patch |\n| Write regression test | `WRITE` | Test patch |\n| Verify behavior | `VALIDATE` | Tests\u002Fchecks |\n| Report result | `NOTIFY` | Root-cause summary |\n\n### Tools and instruments\n- Project test, lint, typecheck, runtime, and logging commands\n- Configured code-intelligence symbol\u002Freference\u002Fpattern search with native fallback\n- Debugging checklist and bug report template\n\n### Canonical workflow path\n```bash\nrg \"\u003Cerror-message-or-symbol>\"\nrg --files\n```\n\nThen run the smallest reproduction command first, add a regression test, and re-run the failing check plus related tests.\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `CODEBASE` | Failing source, tests, and related patterns |\n| `LOCAL_FS` | Bug reports and result artifacts |\n| `PROCESS` | Reproduction and verification commands |\n| `MEMORY` | Hypotheses, root-cause notes, verification evidence |\n\n### Preconditions\n- A bug signal, symptom, or failing behavior is available.\n- Relevant code and verification path can be inspected or the blocker is stated.\n\n### Effects and side effects\n- Mutates source\u002Ftests only as needed for the fix.\n- May create bug documentation under `.agents\u002Fresults\u002Fbugs\u002F`.\n\n### Guardrails\n1. Reproduce first, then diagnose - never guess at fixes\n2. Identify root cause, not just symptoms\n3. Minimal fix: change only what's necessary\n4. Every fix gets a regression test\n5. Search for similar patterns elsewhere after fixing\n6. Document in `.agents\u002Fresults\u002Fbugs\u002F`\n\n### Code intelligence\nUse the configured provider to locate the failing function, find callers, and search similar error patterns. Native search and scoped reads are supported fallbacks; see the shared capability contract.\n\n## References\n- Local code tools: `..\u002F_shared\u002Fcore\u002Fcode-intelligence.md` (code search\u002Fnavigation)\n\n- Execution steps (follow for the selected task): `resources\u002Fexecution-protocol.md`\n- Checklist (pre-submit self-verification): `resources\u002Fchecklist.md`\n- Error recovery: `resources\u002Ferror-playbook.md`\n- Bug report template: `resources\u002Fbug-report-template.md`\n- Common patterns: `resources\u002Fcommon-patterns.md`\n- Debugging checklist (investigation guide, used during Steps 1-2): `resources\u002Fdebugging-checklist.md`\n- Context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Context budget: `..\u002F_shared\u002Fcore\u002Fcontext-budget.md`\n- Lessons learned: `..\u002F_shared\u002Fcore\u002Flessons-learned.md`\n- Observability handoff: `..\u002Foma-observability\u002FSKILL.md` §Integrations — traces\u002Flogs by `trace_id`, 6-dim forensics","# Debug Agent - Bug Fixing Specialist\n\n## Scheduling\n\n### Goal\nReproduce, diagnose, minimally fix, and regression-test bugs while preserving scope discipline and documenting root cause.\n\n### Intent signature\n- User reports a bug, crash, traceback, exception, error message, performance issue, intermittent failure, or regression.\n- User needs root cause analysis plus a minimal code fix and regression test.\n\n### When to use\n- User reports a bug with error messages\n- Something is broken and needs fixing\n- Performance issues or slowdowns\n- Intermittent failures or race conditions\n- Regression bugs\n\n### When NOT to use\n- Building new features -> use Frontend\u002FBackend\u002FMobile agents\n- General code review -> use QA Agent\n\n### Expected inputs\n- Error message, failing behavior, reproduction steps, logs, test failure, or affected code path\n- Existing tests, stack traces, environment notes, and suspected regression boundary\n\n### Expected outputs\n- Root cause explanation\n- Minimal fix scoped to the failing behavior\n- Regression test or explicit reason it cannot be added\n- Bug documentation under `.agents\u002Fresults\u002Fbugs\u002F` when appropriate\n\n### Dependencies\n- `resources\u002Fexecution-protocol.md`, examples, checklist, common patterns, and debugging checklist\n- Local codebase search and symbol\u002Freference tools\n- Project test, lint, typecheck, and runtime commands\n\n### Control-flow features\n- Branches by reproduction success, error class, suspected layer, and verification outcome\n- Reads logs\u002Fcode\u002Ftests and writes code\u002Ftests\u002Fdocs\n- Must search for similar patterns after fixing\n\n## Structural Flow\n\n### Entry\n1. Capture the reported symptom and suspected scope.\n2. Reproduce or establish the closest reliable failing signal.\n3. Identify affected files, tests, and related patterns.\n\n### Scenes\n1. **PREPARE**: Gather symptoms, logs, reproduction path, and verification command.\n2. **ACQUIRE**: Read failing code, tests, references, and similar patterns.\n3. **REASON**: Isolate root cause and reject unsupported hypotheses.\n4. **ACT**: Apply minimal fix and regression test.\n5. **VERIFY**: Re-run failing and related checks.\n6. **FINALIZE**: Document root cause, fix, test, and residual risk.\n\n### Transitions\n- If reproduction fails, use logs\u002Ftests to establish a weaker but explicit diagnostic signal.\n- If the first fix fails verification, return to root-cause analysis.\n- If similar patterns exist, inspect and patch only affected cases.\n- If the request is actually feature work, route to the relevant implementation skill.\n\n### Failure and recovery\n- If environment is missing, document the blocker and provide the closest static diagnosis.\n- If no regression test is feasible, explain why and include manual verification.\n- If fix scope grows, stop and call out the broader design issue.\n\n### Exit\n- Success: bug is fixed, regression coverage exists, and checks pass.\n- Partial success: root cause or verification blocker is explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Reproduce failure | `CALL_TOOL` | Test\u002Fruntime\u002Flog command |\n| Search affected code | `READ` | Code, tests, symbols, references |\n| Compare similar patterns | `COMPARE` | Pattern search |\n| Infer root cause | `INFER` | Diagnostic reasoning |\n| Write minimal fix | `WRITE` | Code patch |\n| Write regression test | `WRITE` | Test patch |\n| Verify behavior | `VALIDATE` | Tests\u002Fchecks |\n| Report result | `NOTIFY` | Root-cause summary |\n\n### Tools and instruments\n- Project test, lint, typecheck, runtime, and logging commands\n- Configured code-intelligence symbol\u002Freference\u002Fpattern search with native fallback\n- Debugging checklist and bug report template\n\n### Canonical workflow path\n```bash\nrg \"\u003Cerror-message-or-symbol>\"\nrg --files\n```\n\nThen run the smallest reproduction command first, add a regression test, and re-run the failing check plus related tests.\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `CODEBASE` | Failing source, tests, and related patterns |\n| `LOCAL_FS` | Bug reports and result artifacts |\n| `PROCESS` | Reproduction and verification commands |\n| `MEMORY` | Hypotheses, root-cause notes, verification evidence |\n\n### Preconditions\n- A bug signal, symptom, or failing behavior is available.\n- Relevant code and verification path can be inspected or the blocker is stated.\n\n### Effects and side effects\n- Mutates source\u002Ftests only as needed for the fix.\n- May create bug documentation under `.agents\u002Fresults\u002Fbugs\u002F`.\n\n### Guardrails\n1. Reproduce first, then diagnose - never guess at fixes\n2. Identify root cause, not just symptoms\n3. Minimal fix: change only what's necessary\n4. Every fix gets a regression test\n5. Search for similar patterns elsewhere after fixing\n6. Document in `.agents\u002Fresults\u002Fbugs\u002F`\n\n### Code intelligence\nUse the configured provider to locate the failing function, find callers, and search similar error patterns. Native search and scoped reads are supported fallbacks; see the shared capability contract.\n\n## References\n- Local code tools: `..\u002F_shared\u002Fcore\u002Fcode-intelligence.md` (code search\u002Fnavigation)\n\n- Execution steps (follow for the selected task): `resources\u002Fexecution-protocol.md`\n- Checklist (pre-submit self-verification): `resources\u002Fchecklist.md`\n- Error recovery: `resources\u002Ferror-playbook.md`\n- Bug report template: `resources\u002Fbug-report-template.md`\n- Common patterns: `resources\u002Fcommon-patterns.md`\n- Debugging checklist (investigation guide, used during Steps 1-2): `resources\u002Fdebugging-checklist.md`\n- Context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Context budget: `..\u002F_shared\u002Fcore\u002Fcontext-budget.md`\n- Lessons learned: `..\u002F_shared\u002Fcore\u002Flessons-learned.md`\n- Observability handoff: `..\u002Foma-observability\u002FSKILL.md` §Integrations — traces\u002Flogs by `trace_id`, 6-dim forensics",{"name":5,"description":7},"master","5fab8004af1390aa17b3447f2780766c8bf2482c",".agents\u002Fskills\u002Foma-debug",0,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate","https:\u002F\u002Fgithub.com\u002Fvasceannie","thingswithstuff.io","2026-11-12 20:22:46",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add vasceannie\u002Fslopgate --skill oma-debug",{"tool":59,"command":60},"bunx","bunx skills add vasceannie\u002Fslopgate --skill oma-debug",{"tool":62,"command":63},"pnpm","pnpm dlx skills add vasceannie\u002Fslopgate --skill oma-debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002FSKILL.md",true,[67,73,77,81,85,89],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"resources\u002Fbug-report-template.md","REFERENCE","参考文档",7617,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Fbug-report-template.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"resources\u002Fchecklist.md",1136,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Fchecklist.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"resources\u002Fcommon-patterns.md",15153,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Fcommon-patterns.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"resources\u002Fdebugging-checklist.md",10529,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Fdebugging-checklist.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"resources\u002Ferror-playbook.md",3451,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Ferror-playbook.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"resources\u002Fexecution-protocol.md",2763,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-debug\u002Fresources\u002Fexecution-protocol.md",[94,125,152,185,210,231],{"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":105,"publishedAt":40},"01M71951JDWCYMS8GDC2C7395D","type-strictness","Enforce strict type compliance by eliminating `Any` types and `# type: ignore` comments. Use when:\n(1) Editing code that contains `Any` as a type annotation\n(2) Code has `# type: ignore` or `# pyright: ignore` comments\n(3) User requests type fixes or type strictness enforcement\n(4) Importing from untyped third-party libraries\n(5) User asks to \"fix types\", \"remove Any\", or \"add proper typing\"\n(6) Pyrefly or mypy reports type errors that need resolution\n(7) Code review reveals weak typing patterns\nFollows hierarchical resolution: codebase inference → type stubs → library inspection → type guards → casting (last resort).","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Ftype-strictness\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[106,107,108,109,110,111,112,28,113,114,115,116,117,118,119,120,121,122,123,124],"type","type strictness","typing","types","remove","code review","fix","inspection","when","code","review","reports","libraries","casting","pyrefly","mypy","pyright","library","patterns",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":40},"01M7194XGBQXSE7Y5BZ4K5CSTK","slopgate-test-extender","Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like \"add tests for X\", \"extend these tests\", \"parametrize tests\", \"consolidate tests\", \"fix test quality\", \"improve test coverage\", \"write tests for this function\", \"test this module\", \"behavior tests\", \"integration tests\", \"missing tests\", \"coverage holes\", \"untested code\", or when a hook denies with test-related findings.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-test-extender\u002FSKILL.md",[131,132],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":133,"categoryName":134,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量",[136,137,138,139,140,112,141,142,143,144,145,146,114,115,147,148,117,149,150,151],"slopgate test extender","test","coverage","fixture","testing","issues","write tests","improve","only","cleanup","loop","candidate","consolidate","references","opencode","orchestrator",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":169,"publishedAt":40},"01M7194RMVQS5YJJ4ZEFXX20VS","slopgate-intelligent-coding-patterns","Pattern-selection playbook for agents editing code with complex branching, stateful parsers\u002Fworkflows, duplicated skeletons, policy checks, or ordered transforms. Load before refactoring if\u002Felif dispatch chains, boolean-flag state machines, repeated validation predicates, parallel provider\u002Flanguage implementations, or regex\u002Fcontent transformation pipelines. Also load when asked to \"apply a design pattern\", \"which pattern should I use here\", \"refactor this switch statement\", \"replace if-elif chain\", \"state machine pattern\", \"strategy pattern\", \"template method\", \"pipeline pattern\", \"specification pattern\", \"dispatch table\", \"guard clause refactor\", \"reduce cyclomatic complexity\", or when Slopgate fires PY-CODE-014, PY-CODE-017, PY-CODE-018, QUALITY-LINT-001, or PY-QUALITY-010. Use with behavior-locking tests and avoid pattern theater for simple one-off code.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-intelligent-coding-patterns\u002FSKILL.md",[158,159,162,165,166],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":160,"categoryName":161,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":163,"categoryName":164,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[170,171,124,172,173,174,175,176,177,178,179,180,181,144,145,182,183,114,184,115],"coding patterns","slopgate intelligent coding patterns","coding","stateful","complexity","branch","which","chain","parsers","pipeline","selection","design","utility","workflows","reduce",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":193,"publishedAt":40},"01M7194KTXBM85GB0W7JKFQD55","slopgate-hygiene-orchestrator","Orchestrate systematic elimination of linter warnings and errors across Python, TypeScript, and Rust codebases. Use when asked to \"clean up lints\", \"fix all warnings\", \"run hygiene\", \"eliminate type errors\", \"orchestrate code quality fixes\", \"fix lint errors\", \"resolve quality gate failures\", \"pass CI checks\", \"reduce tech debt\", \"refactor to pass hooks\", or when a Slopgate hook denies with QUALITY-LINT-001, PY-CODE-017, PY-CODE-018, or any collector finding. This skill coordinates multiple code-hygiene-enforcer agents working in parallel on non-conflicting file groupings, tracks progress persistently via JSON exports, and loops until all issues are resolved. CRITICAL: Never run linters directly—always use `slopgate lint check` as the primary gate, discover project-specific tools from config files, and export findings to JSON for tracking.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-hygiene-orchestrator\u002FSKILL.md",[191,192],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":163,"categoryName":164,"taxonomyType":103,"taxonomyTypeDesc":104},[194,195,151,196,112,197,198,199,200,201,145,184,202,203,204,205,206,207,208,209],"slopgate hygiene orchestrator","hygiene","project","ci","local","clean","never run","files","run","lint check","systematic","config","typescript","debt","quality-gates","hook",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":218,"publishedAt":40},"01M7194G50FZYXXT8VNK360RPA","slopgate-code-smell-utility-locator","Autoactivate when code-smell hooks or reviews mention feature envy, thin wrappers, duplicate helpers, duplicate code,\nscattered helpers, builders\u002Ffactories\u002Fconfig\u002Fconstants\u002Fdataclass reuse, PY-CODE-012, PY-CODE-013, QUALITY-LINT-001,\nor repeated slopgate code-quality denials. Also load when asked to \"find existing helpers\", \"consolidate utilities\",\n\"search for duplicate code\", \"where is this already implemented\", \"reuse existing logic\", \"don't duplicate this\",\n\"find similar functions\", \"utility inventory\", \"code smell radar\", or before adding new helpers\u002Fwrappers so agents can\nfind existing shared utilities and consolidate instead of duplicating.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-smell-utility-locator\u002FSKILL.md",[216,217],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[182,219,115,220,138,221,222,223,224,144,225,114,226,148,150,227,228,205,229,230],"slopgate code smell utility locator","shared","reviews","inventory","search","hooks","new","coordination","radar","code-quality","Utilities","dataclass",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":239,"publishedAt":40},"01M7194AWG1Q37F9756H4SFDH9","slopgate-code-hygiene-refactor","Recovery playbook for Slopgate and project quality failures. Load after hook\u002Flint denials such as PY-CODE-017 flat sibling modules, PY-CODE-018 oversized modules, QUALITY-LINT-001 post-edit quality backstops, PY-QUALITY-010 magic numbers \u002F repeated literals, PY-CODE-012\u002FPY-CODE-013 smell findings, type-suppression bans, duplicate helpers, or repeated hygiene retry loops. Also load when asked to \"refactor this module\", \"split this file\", \"extract a class\", \"reduce complexity\", \"fix god class\", \"flatten module hierarchy\", \"move code to a package\", \"extract helpers\", \"consolidate duplicates\", \"replace magic numbers with constants\", or when a hook blocks an edit with structural complaints. Focuses on preserving public APIs while refactoring toward packages, cohesive modules, typed seams, and focused tests.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-hygiene-refactor\u002FSKILL.md",[237,238],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[240,241,115,242,195,243,174,244,245,196,246,222,247,112,144,182,114,184,226,148],"code hygiene","slopgate code hygiene refactor","refactor","modules","duplicates","retry","move","structural"]