[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DG2979BY8K3XCBFZ5CWQCF":3,"skill-same:01M6DG2979BY8K3XCBFZ5CWQCF":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":13,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M6DG2979BY8K3XCBFZ5CWQCF","get-qodo-rules",null,"Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.","mbaker95\u002Fnanodex","mbaker95","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11398294?v=4","01M6DFXVNAJHZG78Y2D700Y6V3","01M6DFXVTTW83QGKTJ9FJ5YCH5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fget-qodo-rules\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"get qodo rules","get","Rules","repo","feature","generation","task","build","standards","use","fix","fetch","review","Bash","team","planning","code","create","tasks","implement","2026-11-10 10:12:30",false,"---\nname: get-qodo-rules\ndescription: \"Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.\"\nversion: 2.0.0\nallowed-tools: [\"Bash\"]\ntriggers:\n  - \"get.?qodo.?rules\"\n  - \"get.?rules\"\n  - \"load.?qodo.?rules\"\n  - \"load.?rules\"\n  - \"fetch.?qodo.?rules\"\n  - \"fetch.?rules\"\n  - \"qodo.?rules\"\n  - \"coding.?rules\"\n  - \"code.?rules\"\n  - \"before.?cod\"\n  - \"start.?coding\"\n  - \"write.?code\"\n  - \"implement\"\n  - \"create.*code\"\n  - \"build.*feature\"\n  - \"add.*feature\"\n  - \"fix.*bug\"\n  - \"refactor\"\n  - \"modify.*code\"\n  - \"update.*code\"\n---\n\n# Get Qodo Rules Skill\n\n## Description\n\nFetches repository-specific coding rules from the Qodo platform API before code generation or modification tasks. Rules include security requirements, coding standards, quality guidelines, and team conventions that must be applied during code generation.\n**Use** before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.\n**Skip** if \"Qodo Rules Loaded\" already appears in conversation context\n\n---\n\n## Workflow\n\n### Step 1: Check if Rules Already Loaded\n\nIf rules are already loaded (look for \"Qodo Rules Loaded\" in recent messages), skip to step 6.\n\n### Step 2: Verify working in a git repository\n\n- Check that the current directory is inside a git repository. If not, inform the user that a git repository is required and exit gracefully.\n- Extract the repository scope from the git `origin` remote URL. If no remote is found, exit silently. If the URL cannot be parsed, inform the user and exit gracefully.\n- Detect module-level scope: if inside a `modules\u002F*` subdirectory, use it as the query scope; otherwise use repository-wide scope.\n\nSee [repository scope detection](references\u002Frepository-scope.md) for details.\n\n### Step 3: Verify Qodo Configuration\n\nCheck that the required Qodo configuration is present. The default location is `~\u002F.qodo\u002Fconfig.json`.\n\n- **API key**: Read from `~\u002F.qodo\u002Fconfig.json` (`API_KEY` field). If not found, inform the user that an API key is required and provide setup instructions, then exit gracefully.\n- **Environment name**: Read from `~\u002F.qodo\u002Fconfig.json` (`ENVIRONMENT_NAME` field), with `QODO_ENVIRONMENT_NAME` environment variable taking precedence. If not found, inform the user that an API key is required and provide setup instructions, then exit gracefully.\n\n### Step 4: Fetch Rules with Pagination\n\n- Fetch all pages from the API (50 rules per page) until no more results are returned.\n- On each page, handle HTTP errors and exit gracefully with a user-friendly message.\n- Accumulate all rules across pages into a single list.\n- Stop after 100 pages maximum (safety limit).\n- If no rules are found after all pages, inform the user and exit gracefully.\n\nSee [pagination details](references\u002Fpagination.md) for the full algorithm and error handling.\n\n### Step 5: Format and Output Rules\n\n- Print the \"? Qodo Rules Loaded\" header with repository scope, scope context, and total rule count.\n- Group rules by severity and print each non-empty group: ERROR, WARNING, RECOMMENDATION.\n- Each rule is formatted as: `- **{name}** ({category}): {description}`\n- End output with `---`.\n\nSee [output format details](references\u002Foutput-format.md) for the exact format.\n\n### Step 6: Apply Rules by Severity\n\n| Severity | Enforcement | When Skipped |\n|---|---|---|\n| **ERROR** | Must comply, non-negotiable. Add comment documenting compliance (e.g., `# Following Qodo rule: No Hardcoded Credentials`) | Explain to user and ask for guidance |\n| **WARNING** | Should comply by default | Briefly explain why in response |\n| **RECOMMENDATION** | Consider when appropriate | No action needed |\n\n### Step 7: Report\n\nAfter code generation, inform the user about rule application:\n- **ERROR rules applied**: List which rules were followed\n- **WARNING rules skipped**: Explain why\n- **No rules applicable**: Inform: \"No Qodo rules were applicable to this code change\"\n- **RECOMMENDATION rules**: Mention only if they influenced a design decision\n\n---\n\n## How Scope Levels Work\n\nDetermines scope from git remote and working directory (see [Step 2](#step-2-verify-working-in-a-git-repository)):\n\n**Scope Hierarchy**:\n- **Universal** (`\u002F`) - applies everywhere\n- **Org Level** (`\u002Forg\u002F`) - applies to organization\n- **Repo Level** (`\u002Forg\u002Frepo\u002F`) - applies to repository\n- **Path Level** (`\u002Forg\u002Frepo\u002Fpath\u002F`) - applies to specific paths\n\n---\n\n## Configuration\n\nSee `~\u002F.qodo\u002Fconfig.json` for API key setup. Set `QODO_ENVIRONMENT_NAME` env var or `ENVIRONMENT_NAME` in config to select environment.\n\n---\n\n## Common Mistakes\n\n- **Re-running when rules are loaded** - Check for \"Qodo Rules Loaded\" in context first\n- **Missing compliance comments on ERROR rules** - ERROR rules require a comment documenting compliance\n- **Forgetting to report when no rules apply** - Always inform the user when no rules were applicable, so they know the rules system is active\n- **Not in git repo** - Inform the user that a git repository is required and exit gracefully; do not attempt code generation\n- **No API key** - Inform the user with setup instructions; set `QODO_API_KEY` or create `~\u002F.qodo\u002Fconfig.json`\n- **No rules found** - Inform the user; set up rules at app.qodo.ai\n","# Get Qodo Rules Skill\n\n## Description\n\nFetches repository-specific coding rules from the Qodo platform API before code generation or modification tasks. Rules include security requirements, coding standards, quality guidelines, and team conventions that must be applied during code generation.\n**Use** before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.\n**Skip** if \"Qodo Rules Loaded\" already appears in conversation context\n\n---\n\n## Workflow\n\n### Step 1: Check if Rules Already Loaded\n\nIf rules are already loaded (look for \"Qodo Rules Loaded\" in recent messages), skip to step 6.\n\n### Step 2: Verify working in a git repository\n\n- Check that the current directory is inside a git repository. If not, inform the user that a git repository is required and exit gracefully.\n- Extract the repository scope from the git `origin` remote URL. If no remote is found, exit silently. If the URL cannot be parsed, inform the user and exit gracefully.\n- Detect module-level scope: if inside a `modules\u002F*` subdirectory, use it as the query scope; otherwise use repository-wide scope.\n\nSee [repository scope detection](references\u002Frepository-scope.md) for details.\n\n### Step 3: Verify Qodo Configuration\n\nCheck that the required Qodo configuration is present. The default location is `~\u002F.qodo\u002Fconfig.json`.\n\n- **API key**: Read from `~\u002F.qodo\u002Fconfig.json` (`API_KEY` field). If not found, inform the user that an API key is required and provide setup instructions, then exit gracefully.\n- **Environment name**: Read from `~\u002F.qodo\u002Fconfig.json` (`ENVIRONMENT_NAME` field), with `QODO_ENVIRONMENT_NAME` environment variable taking precedence. If not found, inform the user that an API key is required and provide setup instructions, then exit gracefully.\n\n### Step 4: Fetch Rules with Pagination\n\n- Fetch all pages from the API (50 rules per page) until no more results are returned.\n- On each page, handle HTTP errors and exit gracefully with a user-friendly message.\n- Accumulate all rules across pages into a single list.\n- Stop after 100 pages maximum (safety limit).\n- If no rules are found after all pages, inform the user and exit gracefully.\n\nSee [pagination details](references\u002Fpagination.md) for the full algorithm and error handling.\n\n### Step 5: Format and Output Rules\n\n- Print the \"? Qodo Rules Loaded\" header with repository scope, scope context, and total rule count.\n- Group rules by severity and print each non-empty group: ERROR, WARNING, RECOMMENDATION.\n- Each rule is formatted as: `- **{name}** ({category}): {description}`\n- End output with `---`.\n\nSee [output format details](references\u002Foutput-format.md) for the exact format.\n\n### Step 6: Apply Rules by Severity\n\n| Severity | Enforcement | When Skipped |\n|---|---|---|\n| **ERROR** | Must comply, non-negotiable. Add comment documenting compliance (e.g., `# Following Qodo rule: No Hardcoded Credentials`) | Explain to user and ask for guidance |\n| **WARNING** | Should comply by default | Briefly explain why in response |\n| **RECOMMENDATION** | Consider when appropriate | No action needed |\n\n### Step 7: Report\n\nAfter code generation, inform the user about rule application:\n- **ERROR rules applied**: List which rules were followed\n- **WARNING rules skipped**: Explain why\n- **No rules applicable**: Inform: \"No Qodo rules were applicable to this code change\"\n- **RECOMMENDATION rules**: Mention only if they influenced a design decision\n\n---\n\n## How Scope Levels Work\n\nDetermines scope from git remote and working directory (see [Step 2](#step-2-verify-working-in-a-git-repository)):\n\n**Scope Hierarchy**:\n- **Universal** (`\u002F`) - applies everywhere\n- **Org Level** (`\u002Forg\u002F`) - applies to organization\n- **Repo Level** (`\u002Forg\u002Frepo\u002F`) - applies to repository\n- **Path Level** (`\u002Forg\u002Frepo\u002Fpath\u002F`) - applies to specific paths\n\n---\n\n## Configuration\n\nSee `~\u002F.qodo\u002Fconfig.json` for API key setup. Set `QODO_ENVIRONMENT_NAME` env var or `ENVIRONMENT_NAME` in config to select environment.\n\n---\n\n## Common Mistakes\n\n- **Re-running when rules are loaded** - Check for \"Qodo Rules Loaded\" in context first\n- **Missing compliance comments on ERROR rules** - ERROR rules require a comment documenting compliance\n- **Forgetting to report when no rules apply** - Always inform the user when no rules were applicable, so they know the rules system is active\n- **Not in git repo** - Inform the user that a git repository is required and exit gracefully; do not attempt code generation\n- **No API key** - Inform the user with setup instructions; set `QODO_API_KEY` or create `~\u002F.qodo\u002Fconfig.json`\n- **No rules found** - Inform the user; set up rules at app.qodo.ai\n",{"name":5,"version":48,"triggers":49,"description":7,"allowed-tools":69},"2.0.0",[50,51,52,53,54,55,56,57,58,59,60,61,42,62,63,64,65,66,67,68],"get.?qodo.?rules","get.?rules","load.?qodo.?rules","load.?rules","fetch.?qodo.?rules","fetch.?rules","qodo.?rules","coding.?rules","code.?rules","before.?cod","start.?coding","write.?code","create.*code","build.*feature","add.*feature","fix.*bug","refactor","modify.*code","update.*code",[36],"main","b6b2f4d4a0c7243409d1684119a6772629bfeba6",".claude\u002Fskills\u002Fget-qodo-rules","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex","https:\u002F\u002Fgithub.com\u002Fmbaker95","2026-03-12 23:02:12",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add mbaker95\u002Fnanodex --skill get-qodo-rules",{"tool":82,"command":83},"bunx","bunx skills add mbaker95\u002Fnanodex --skill get-qodo-rules",{"tool":85,"command":86},"pnpm","pnpm dlx skills add mbaker95\u002Fnanodex --skill get-qodo-rules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fget-qodo-rules\u002FSKILL.md",true,[90,96,100],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Foutput-format.md","REFERENCE","参考文档",842,"https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fget-qodo-rules\u002Freferences\u002Foutput-format.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fpagination.md",1289,"https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fget-qodo-rules\u002Freferences\u002Fpagination.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Frepository-scope.md",964,"https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fget-qodo-rules\u002Freferences\u002Frepository-scope.md",[105,131,150,173,185,197],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":43},"01M6DG2XYNH5XV7XGTJJ1SF0TG","agent-browser","Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fagent-browser\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[115,116,117,118,29,119,120,32,121,122,123,124,125,126,127,128,129,36,130],"agent browser","browser","pages","forms","test web","take","extract","data","user","read","screenshots","research","test","web","just","browse",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":43},"01M6DG2TPZAT3SMWSYFJ3K82TE","x-integration","X (Twitter) integration for NanoClaw. Post tweets, like, reply, retweet, and quote. Use for setup, testing, or troubleshooting X functionality. Triggers on \"setup x\", \"x integration\", \"twitter\", \"post tweet\", \"tweet\".","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fx-integration\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",[141,142,32,143,144,145,146,147,148,149],"x integration","integration","testing","setup","troubleshooting","twitter","reply","quote","triggers",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":43},"01M6DG2Q4BJQ046BZSR9N7GZ72","use-local-whisper","Use when the user wants local voice transcription instead of OpenAI Whisper API. Switches to whisper.cpp running on Apple Silicon. WhatsApp only for now. Requires voice-transcription skill to be applied first.","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fuse-local-whisper\u002FSKILL.md",[],[157,158,32,159,160,161,162,163,123,164,165,166,167,168,169,170,171,172],"whisper","local whisper","local","use local whisper","apple","openai whisper","only","voice","apple silicon","api","first","openai","cpp","transcription","openai whisper api","whatsapp",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":43},"01M6DG2N2Z1V8VV4MQFRKFAQV0","update-skills","Check for and apply updates to installed skill branches from upstream.","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[180,181,182,183,184],"update","update skills","upstream","branches","check",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":43},"01M6DG2J5D7Y3R2BF8V87XZAXF","update-nanoclaw","Efficiently bring upstream NanoClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupdate-nanoclaw\u002FSKILL.md",[],[180,192,193,194,182,195,196],"update nanoclaw","install","pick","token","preview",{"skillNo":198,"name":144,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":43},"01M6DG2FN7S7DVD337CNT5Y67D","Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on \"setup\", \"install\", \"configure nanoclaw\", or first-time setup requests.","https:\u002F\u002Fgithub.com\u002Fmbaker95\u002Fnanodex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup\u002FSKILL.md",[],[144,193,149,203,204,70,32,205,123,206,167,207,208,209,210],"time","dependencies","channel","configure","services","start","messaging","run"]