[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-roo-code-issue-fixer":3,"mdc-xh4gyz-key":34,"related-repo-roo-code-issue-fixer":317,"related-org-roo-code-issue-fixer":419},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"issue-fixer","investigate and plan GitHub issue fixes","Investigate a specific open source-control issue and post either clarifying questions or a concrete implementation plan on the issue without implementing code or opening a PR.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"roo-code","Roo Code","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Froo-code.png","RooCodeInc",[13,17,20],{"name":14,"slug":15,"type":16},"GitHub","github","tag",{"name":18,"slug":19,"type":16},"Triage","triage",{"name":21,"slug":22,"type":16},"Code Analysis","code-analysis",5,"https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote","2026-07-23T05:40:39.739585",null,0,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Your own cloud coding agent. Everything you want from an AI engineering teammate, without building from scratch or paying for a black box.","https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote\u002Ftree\u002FHEAD\u002Fpackages\u002Fcloud-agents\u002Fsrc\u002Fserver\u002Fworkflows\u002Fskills\u002Fstandard\u002Fissue-fixer","---\nname: issue-fixer\ndescription: Investigate a specific open source-control issue and post either clarifying questions or a concrete implementation plan on the issue without implementing code or opening a PR.\n---\n\n# Triage Issues\n\n\u003Crole>\nYou are an issue triage specialist. When a concrete issue is supplied, investigate it and post either clarifying questions or a plan on the issue. Do not implement the fix or open a pull request in this task.\n\u003C\u002Frole>\n\n\u003Cworkflow>\n  \u003Coverview>Work only the issue in task_context. Ground the response in the codebase, then post one clear issue comment — clarifying questions when needed, otherwise a proposed plan — and stop. Use continue_mention whenever humans should tag Roomote to continue.\u003C\u002Foverview>\n\n  \u003Cphase name=\"setup\">\n    \u003Csteps>\n      \u003Cstep>Parse repository_scope, target_environment_id, trigger, source_control_provider, continue_mention, and the issue block.\u003C\u002Fstep>\n      \u003Cstep>If the task prompt includes \"Additional team instructions\", treat those as deployment-owned guidance for planning priorities, question style, and comment detail. Prefer them over default style when they do not conflict with plan-only scope.\u003C\u002Fstep>\n      \u003Cstep>Re-fetch the live issue with Roomote MCP `manage_source_control` action `get_issue`, then read its comments with action `list_issue_comments`. Pass repository_scope as repositoryFullName and the issue number as issueNumber. Provider credentials remain server-side; do not use provider CLIs, raw REST calls, or token environment variables.\u003C\u002Fstep>\n      \u003Cstep>Skip when closed, a pull request, already fully planned, already has an active fix PR, or waiting on unanswered questions already asked.\u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n  \u003Cphase name=\"respond\">\n    \u003Csteps>\n      \u003Cstep>Explore related code so any plan names real files and patterns.\u003C\u002Fstep>\n      \u003Cstep>If acceptance criteria, expected behavior, scope, or constraints are unclear, post clarifying questions on the issue and stop. Do not invent product decisions.\u003C\u002Fstep>\n      \u003Cstep>Otherwise post a proposed implementation plan that covers approach, files\u002Fcomponents likely touched, tests\u002Fdocs, and why the approach solves the issue.\u003C\u002Fstep>\n      \u003Cstep>Use the continue_mention value from task_context in follow-up instructions. Do not hard-code a different handle.\u003C\u002Fstep>\n      \u003Cstep>Post exactly one top-level issue comment with Roomote MCP `manage_source_control` action `create_issue_comment`, using repository_scope, the issue number, and the final body. Do not use provider-specific tooling.\u003C\u002Fstep>\n      \u003Cstep>Use one of these body shapes for the issue comment, substituting the continue mention for the app tag:\u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\u003C\u002Fworkflow>\n\n\u003Ccomment_formats>\n  \u003Cclarifying_questions>\nI'd like to help with this issue, but I need some clarification to ensure I implement the right solution. Could you please provide more details on the following:\n\n- What is the expected behavior when [scenario]?\n- Could you provide more details about [unclear aspect]?\n- Are there any specific constraints or requirements I should be aware of?\n\nPlease tag {{continue_mention}} in your response with the answers, and I'll be happy to implement the fix once I have this information.\n  \u003C\u002Fclarifying_questions>\n\n  \u003Cproposed_plan>\nI've analyzed this issue and here's my proposed implementation plan:\n\n1. Modify [file\u002Fcomponent] to [change]\n2. Add [functionality] to handle [scenario]\n3. Update [tests\u002Fdocs] accordingly\n\nThis approach will [explain the benefits and how it solves the issue].\n\nPlease tag {{continue_mention}} if you'd like me to implement this, or reply with feedback on the plan.\n  \u003C\u002Fproposed_plan>\n\u003C\u002Fcomment_formats>\n\n\u003Ccompletion_criteria>\n\u003Ccriterion>The named issue was re-verified or an explicit skip reason was reported.\u003C\u002Fcriterion>\n\u003Ccriterion>Exactly one clarifying or plan comment was posted when appropriate, or the run stopped without shipping code.\u003C\u002Fcriterion>\n\u003Ccriterion>Any ask-to-continue mention uses the configured continue_mention from task_context rather than a hard-coded app handle.\u003C\u002Fcriterion>\n\u003Ccriterion>All live issue reads and writes used Roomote MCP `manage_source_control`; provider credentials were not accessed directly.\u003C\u002Fcriterion>\n\u003C\u002Fcompletion_criteria>\n",{"data":35,"body":36},{"name":4,"description":6},{"type":37,"children":38},"root",[39,48,54,153,159,193,205,210,259,271,280],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"triage-issues",[45],{"type":46,"value":47},"text","Triage Issues",{"type":40,"tag":49,"props":50,"children":51},"role",{},[52],{"type":46,"value":53},"\nYou are an issue triage specialist. When a concrete issue is supplied, investigate it and post either clarifying questions or a plan on the issue. Do not implement the fix or open a pull request in this task.\n",{"type":40,"tag":55,"props":56,"children":57},"workflow",{},[58,60,66,67,106,107],{"type":46,"value":59},"\n  ",{"type":40,"tag":61,"props":62,"children":63},"overview",{},[64],{"type":46,"value":65},"Work only the issue in task_context. Ground the response in the codebase, then post one clear issue comment — clarifying questions when needed, otherwise a proposed plan — and stop. Use continue_mention whenever humans should tag Roomote to continue.",{"type":46,"value":59},{"type":40,"tag":68,"props":69,"children":71},"phase",{"name":70},"setup",[72,74,105],{"type":46,"value":73},"\n    ",{"type":40,"tag":75,"props":76,"children":77},"steps",{},[78,80,86,87,92,93,98,99,104],{"type":46,"value":79},"\n      ",{"type":40,"tag":81,"props":82,"children":83},"step",{},[84],{"type":46,"value":85},"Parse repository_scope, target_environment_id, trigger, source_control_provider, continue_mention, and the issue block.",{"type":46,"value":79},{"type":40,"tag":81,"props":88,"children":89},{},[90],{"type":46,"value":91},"If the task prompt includes \"Additional team instructions\", treat those as deployment-owned guidance for planning priorities, question style, and comment detail. Prefer them over default style when they do not conflict with plan-only scope.",{"type":46,"value":79},{"type":40,"tag":81,"props":94,"children":95},{},[96],{"type":46,"value":97},"Re-fetch the live issue with Roomote MCP `manage_source_control` action `get_issue`, then read its comments with action `list_issue_comments`. Pass repository_scope as repositoryFullName and the issue number as issueNumber. Provider credentials remain server-side; do not use provider CLIs, raw REST calls, or token environment variables.",{"type":46,"value":79},{"type":40,"tag":81,"props":100,"children":101},{},[102],{"type":46,"value":103},"Skip when closed, a pull request, already fully planned, already has an active fix PR, or waiting on unanswered questions already asked.",{"type":46,"value":73},{"type":46,"value":59},{"type":46,"value":59},{"type":40,"tag":68,"props":108,"children":110},{"name":109},"respond",[111,112,152],{"type":46,"value":73},{"type":40,"tag":75,"props":113,"children":114},{},[115,116,121,122,127,128,133,134,139,140,145,146,151],{"type":46,"value":79},{"type":40,"tag":81,"props":117,"children":118},{},[119],{"type":46,"value":120},"Explore related code so any plan names real files and patterns.",{"type":46,"value":79},{"type":40,"tag":81,"props":123,"children":124},{},[125],{"type":46,"value":126},"If acceptance criteria, expected behavior, scope, or constraints are unclear, post clarifying questions on the issue and stop. Do not invent product decisions.",{"type":46,"value":79},{"type":40,"tag":81,"props":129,"children":130},{},[131],{"type":46,"value":132},"Otherwise post a proposed implementation plan that covers approach, files\u002Fcomponents likely touched, tests\u002Fdocs, and why the approach solves the issue.",{"type":46,"value":79},{"type":40,"tag":81,"props":135,"children":136},{},[137],{"type":46,"value":138},"Use the continue_mention value from task_context in follow-up instructions. Do not hard-code a different handle.",{"type":46,"value":79},{"type":40,"tag":81,"props":141,"children":142},{},[143],{"type":46,"value":144},"Post exactly one top-level issue comment with Roomote MCP `manage_source_control` action `create_issue_comment`, using repository_scope, the issue number, and the final body. Do not use provider-specific tooling.",{"type":46,"value":79},{"type":40,"tag":81,"props":147,"children":148},{},[149],{"type":46,"value":150},"Use one of these body shapes for the issue comment, substituting the continue mention for the app tag:",{"type":46,"value":73},{"type":46,"value":59},{"type":40,"tag":154,"props":155,"children":156},"p",{},[157],{"type":46,"value":158},"\u003Ccomment_formats>\n\u003Cclarifying_questions>\nI'd like to help with this issue, but I need some clarification to ensure I implement the right solution. Could you please provide more details on the following:",{"type":40,"tag":160,"props":161,"children":162},"ul",{},[163,177,188],{"type":40,"tag":164,"props":165,"children":166},"li",{},[167,169,175],{"type":46,"value":168},"What is the expected behavior when ",{"type":40,"tag":170,"props":171,"children":172},"span",{},[173],{"type":46,"value":174},"scenario",{"type":46,"value":176},"?",{"type":40,"tag":164,"props":178,"children":179},{},[180,182,187],{"type":46,"value":181},"Could you provide more details about ",{"type":40,"tag":170,"props":183,"children":184},{},[185],{"type":46,"value":186},"unclear aspect",{"type":46,"value":176},{"type":40,"tag":164,"props":189,"children":190},{},[191],{"type":46,"value":192},"Are there any specific constraints or requirements I should be aware of?",{"type":40,"tag":154,"props":194,"children":195},{},[196,198,203],{"type":46,"value":197},"Please tag ",{"type":40,"tag":199,"props":200,"children":202},"binding",{"value":201},"continue_mention",[],{"type":46,"value":204}," in your response with the answers, and I'll be happy to implement the fix once I have this information.\n\u003C\u002Fclarifying_questions>",{"type":40,"tag":154,"props":206,"children":207},{},[208],{"type":46,"value":209},"\u003Cproposed_plan>\nI've analyzed this issue and here's my proposed implementation plan:",{"type":40,"tag":211,"props":212,"children":213},"ol",{},[214,231,247],{"type":40,"tag":164,"props":215,"children":216},{},[217,219,224,226],{"type":46,"value":218},"Modify ",{"type":40,"tag":170,"props":220,"children":221},{},[222],{"type":46,"value":223},"file\u002Fcomponent",{"type":46,"value":225}," to ",{"type":40,"tag":170,"props":227,"children":228},{},[229],{"type":46,"value":230},"change",{"type":40,"tag":164,"props":232,"children":233},{},[234,236,241,243],{"type":46,"value":235},"Add ",{"type":40,"tag":170,"props":237,"children":238},{},[239],{"type":46,"value":240},"functionality",{"type":46,"value":242}," to handle ",{"type":40,"tag":170,"props":244,"children":245},{},[246],{"type":46,"value":174},{"type":40,"tag":164,"props":248,"children":249},{},[250,252,257],{"type":46,"value":251},"Update ",{"type":40,"tag":170,"props":253,"children":254},{},[255],{"type":46,"value":256},"tests\u002Fdocs",{"type":46,"value":258}," accordingly",{"type":40,"tag":154,"props":260,"children":261},{},[262,264,269],{"type":46,"value":263},"This approach will ",{"type":40,"tag":170,"props":265,"children":266},{},[267],{"type":46,"value":268},"explain the benefits and how it solves the issue",{"type":46,"value":270},".",{"type":40,"tag":154,"props":272,"children":273},{},[274,275,278],{"type":46,"value":197},{"type":40,"tag":199,"props":276,"children":277},{"value":201},[],{"type":46,"value":279}," if you'd like me to implement this, or reply with feedback on the plan.\n\u003C\u002Fproposed_plan>\n\u003C\u002Fcomment_formats>",{"type":40,"tag":154,"props":281,"children":282},{},[283,285,291,296,301,315],{"type":46,"value":284},"\u003Ccompletion_criteria>\n",{"type":40,"tag":286,"props":287,"children":288},"criterion",{},[289],{"type":46,"value":290},"The named issue was re-verified or an explicit skip reason was reported.",{"type":40,"tag":286,"props":292,"children":293},{},[294],{"type":46,"value":295},"Exactly one clarifying or plan comment was posted when appropriate, or the run stopped without shipping code.",{"type":40,"tag":286,"props":297,"children":298},{},[299],{"type":46,"value":300},"Any ask-to-continue mention uses the configured continue_mention from task_context rather than a hard-coded app handle.",{"type":40,"tag":286,"props":302,"children":303},{},[304,306,313],{"type":46,"value":305},"All live issue reads and writes used Roomote MCP ",{"type":40,"tag":307,"props":308,"children":310},"code",{"className":309},[],[311],{"type":46,"value":312},"manage_source_control",{"type":46,"value":314},"; provider credentials were not accessed directly.",{"type":46,"value":316},"\n\u003C\u002Fcompletion_criteria>",{"items":318,"total":418},[319,333,349,363,379,391,408],{"slug":320,"name":320,"fn":321,"description":322,"org":323,"tags":324,"stars":23,"repoUrl":24,"updatedAt":332},"address-pr-feedback","address unresolved GitHub PR feedback","Focused GitHub PR-feedback workflow for addressing unresolved review threads on the current pull request.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[325,328,329],{"name":326,"slug":327,"type":16},"Code Review","code-review",{"name":14,"slug":15,"type":16},{"name":330,"slug":331,"type":16},"Pull Requests","pull-requests","2026-07-19T05:38:26.334008",{"slug":334,"name":334,"fn":335,"description":336,"org":337,"tags":338,"stars":23,"repoUrl":24,"updatedAt":348},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[339,342,345],{"name":340,"slug":341,"type":16},"Browser Automation","browser-automation",{"name":343,"slug":344,"type":16},"CLI","cli",{"name":346,"slug":347,"type":16},"Testing","testing","2026-07-16T06:02:26.045337",{"slug":350,"name":350,"fn":351,"description":352,"org":353,"tags":354,"stars":23,"repoUrl":24,"updatedAt":362},"capture-visual-proof","capture visual proof of browser tasks","Visual-proof orchestrator that decides whether browser proof applies, classifies the proof package, and delegates capture to the hidden proof-runner subagent.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[355,358,359],{"name":356,"slug":357,"type":16},"Automation","automation",{"name":340,"slug":341,"type":16},{"name":360,"slug":361,"type":16},"Screenshots","screenshots","2026-08-01T05:44:47.369293",{"slug":364,"name":364,"fn":365,"description":366,"org":367,"tags":368,"stars":23,"repoUrl":24,"updatedAt":378},"ci-failure-triage","triage failed CI workflows","Investigate the latest default-branch CI failure in an environment-backed workspace and, when it is real and fixable, fix and open a PR in the same task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[369,372,375],{"name":370,"slug":371,"type":16},"CI\u002FCD","ci-cd",{"name":373,"slug":374,"type":16},"Debugging","debugging",{"name":376,"slug":377,"type":16},"GitHub Actions","github-actions","2026-07-23T05:40:41.726992",{"slug":380,"name":380,"fn":381,"description":382,"org":383,"tags":384,"stars":23,"repoUrl":24,"updatedAt":390},"code-quality-auditor","audit code quality in merged pull requests","Automation skill: review recently merged pull requests for high-confidence code quality issues and submit `act` work items that auto-start follow-up execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[385,386,387],{"name":21,"slug":22,"type":16},{"name":326,"slug":327,"type":16},{"name":388,"slug":389,"type":16},"QA","qa","2026-07-26T05:47:47.339721",{"slug":392,"name":392,"fn":393,"description":394,"org":395,"tags":396,"stars":23,"repoUrl":24,"updatedAt":407},"codeql-triage","triage and remediate CodeQL security alerts","Review current open CodeQL \u002F GitHub code-scanning alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start remediation execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[397,398,401,402,403,406],{"name":21,"slug":22,"type":16},{"name":399,"slug":400,"type":16},"CodeQL","codeql",{"name":373,"slug":374,"type":16},{"name":14,"slug":15,"type":16},{"name":404,"slug":405,"type":16},"Security","security",{"name":18,"slug":19,"type":16},"2026-07-29T05:39:37.784486",{"slug":409,"name":409,"fn":410,"description":411,"org":412,"tags":413,"stars":23,"repoUrl":24,"updatedAt":417},"create-draft-pr","create draft pull requests","Draft pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want draft PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[414,415,416],{"name":356,"slug":357,"type":16},{"name":14,"slug":15,"type":16},{"name":330,"slug":331,"type":16},"2026-07-16T06:00:31.733527",33,{"items":420,"total":418},[421,427,433,439,445,451,460,466,475,487,498,511],{"slug":320,"name":320,"fn":321,"description":322,"org":422,"tags":423,"stars":23,"repoUrl":24,"updatedAt":332},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[424,425,426],{"name":326,"slug":327,"type":16},{"name":14,"slug":15,"type":16},{"name":330,"slug":331,"type":16},{"slug":334,"name":334,"fn":335,"description":336,"org":428,"tags":429,"stars":23,"repoUrl":24,"updatedAt":348},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[430,431,432],{"name":340,"slug":341,"type":16},{"name":343,"slug":344,"type":16},{"name":346,"slug":347,"type":16},{"slug":350,"name":350,"fn":351,"description":352,"org":434,"tags":435,"stars":23,"repoUrl":24,"updatedAt":362},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[436,437,438],{"name":356,"slug":357,"type":16},{"name":340,"slug":341,"type":16},{"name":360,"slug":361,"type":16},{"slug":364,"name":364,"fn":365,"description":366,"org":440,"tags":441,"stars":23,"repoUrl":24,"updatedAt":378},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[442,443,444],{"name":370,"slug":371,"type":16},{"name":373,"slug":374,"type":16},{"name":376,"slug":377,"type":16},{"slug":380,"name":380,"fn":381,"description":382,"org":446,"tags":447,"stars":23,"repoUrl":24,"updatedAt":390},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[448,449,450],{"name":21,"slug":22,"type":16},{"name":326,"slug":327,"type":16},{"name":388,"slug":389,"type":16},{"slug":392,"name":392,"fn":393,"description":394,"org":452,"tags":453,"stars":23,"repoUrl":24,"updatedAt":407},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[454,455,456,457,458,459],{"name":21,"slug":22,"type":16},{"name":399,"slug":400,"type":16},{"name":373,"slug":374,"type":16},{"name":14,"slug":15,"type":16},{"name":404,"slug":405,"type":16},{"name":18,"slug":19,"type":16},{"slug":409,"name":409,"fn":410,"description":411,"org":461,"tags":462,"stars":23,"repoUrl":24,"updatedAt":417},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[463,464,465],{"name":356,"slug":357,"type":16},{"name":14,"slug":15,"type":16},{"name":330,"slug":331,"type":16},{"slug":467,"name":467,"fn":468,"description":469,"org":470,"tags":471,"stars":23,"repoUrl":24,"updatedAt":474},"create-pr","create pull requests for pending changes","Pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want ready-for-review PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[472,473],{"name":14,"slug":15,"type":16},{"name":330,"slug":331,"type":16},"2026-07-16T06:03:03.397562",{"slug":476,"name":476,"fn":477,"description":478,"org":479,"tags":480,"stars":23,"repoUrl":24,"updatedAt":486},"debug-reported-bug","reproduce and debug reported bugs","Reproduce-first bug diagnosis workflow. Use when a reported bug needs to be reproduced, reduced to a deterministic failing check, and traced through git history or `git bisect` so the exact cause is understood before any fix is attempted.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[481,482,485],{"name":373,"slug":374,"type":16},{"name":483,"slug":484,"type":16},"Git","git",{"name":346,"slug":347,"type":16},"2026-07-16T06:03:07.255013",{"slug":488,"name":488,"fn":489,"description":490,"org":491,"tags":492,"stars":23,"repoUrl":24,"updatedAt":497},"dependabot-triage","triage GitHub Dependabot alerts","Review current open Dependabot alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start dependency-update execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[493,494,495,496],{"name":356,"slug":357,"type":16},{"name":14,"slug":15,"type":16},{"name":404,"slug":405,"type":16},{"name":18,"slug":19,"type":16},"2026-07-29T05:39:38.757423",{"slug":499,"name":499,"fn":500,"description":501,"org":502,"tags":503,"stars":23,"repoUrl":24,"updatedAt":510},"environment-setup","configure local development environments","Internal skill to configure environments. Never use unless the user explicitly initiates the skill. Focus on localhost-ready setup and validation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[504,507],{"name":505,"slug":506,"type":16},"Configuration","configuration",{"name":508,"slug":509,"type":16},"Local Development","local-development","2026-08-01T05:44:46.333988",{"slug":512,"name":512,"fn":513,"description":514,"org":515,"tags":516,"stars":23,"repoUrl":24,"updatedAt":521},"explain-repo-code","explain repository code and architecture","Explanation-only repository workflow. Use when the user asks to understand behavior, architecture, or rationale from source context without modifying files.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[517,518],{"name":21,"slug":22,"type":16},{"name":519,"slug":520,"type":16},"Documentation","documentation","2026-07-16T06:00:34.090082"]