--- name: get-qodo-rules-a0a654d98535 description: "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." version: 2.0.0 allowed-tools: ["Bash"] triggers: - "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" - "implement" - "create.*code" - "build.*feature" - "add.*feature" - "fix.*bug" - "refactor" - "modify.*code" - "update.*code" --- # Get Qodo Rules Skill ## Description Fetches 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. **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. **Skip** if "Qodo Rules Loaded" already appears in conversation context --- ## Workflow ### Step 1: Check if Rules Already Loaded If rules are already loaded (look for "Qodo Rules Loaded" in recent messages), skip to step 6. ### Step 2: Verify working in a git repository - Check that the current directory is inside a git repository. If not, inform the user that a git repository is required and exit gracefully. - 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. - Detect module-level scope: if inside a `modules/*` subdirectory, use it as the query scope; otherwise use repository-wide scope. See [repository scope detection](references/repository-scope.md) for details. ### Step 3: Verify Qodo Configuration Check that the required Qodo configuration is present. The default location is `~/.qodo/config.json`. - **API key**: Read from `~/.qodo/config.json` (`API_KEY` field). If not found, inform the user that an API key is required and provide setup instructions, then exit gracefully. - **Environment name**: Read from `~/.qodo/config.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. ### Step 4: Fetch Rules with Pagination - Fetch all pages from the API (50 rules per page) until no more results are returned. - On each page, handle HTTP errors and exit gracefully with a user-friendly message. - Accumulate all rules across pages into a single list. - Stop after 100 pages maximum (safety limit). - If no rules are found after all pages, inform the user and exit gracefully. See [pagination details](references/pagination.md) for the full algorithm and error handling. ### Step 5: Format and Output Rules - Print the "📋 Qodo Rules Loaded" header with repository scope, scope context, and total rule count. - Group rules by severity and print each non-empty group: ERROR, WARNING, RECOMMENDATION. - Each rule is formatted as: `- **{name}** ({category}): {description}` - End output with `---`. See [output format details](references/output-format.md) for the exact format. ### Step 6: Apply Rules by Severity | Severity | Enforcement | When Skipped | |---|---|---| | **ERROR** | Must comply, non-negotiable. Add comment documenting compliance (e.g., `# Following Qodo rule: No Hardcoded Credentials`) | Explain to user and ask for guidance | | **WARNING** | Should comply by default | Briefly explain why in response | | **RECOMMENDATION** | Consider when appropriate | No action needed | ### Step 7: Report After code generation, inform the user about rule application: - **ERROR rules applied**: List which rules were followed - **WARNING rules skipped**: Explain why - **No rules applicable**: Inform: "No Qodo rules were applicable to this code change" - **RECOMMENDATION rules**: Mention only if they influenced a design decision --- ## How Scope Levels Work Determines scope from git remote and working directory (see [Step 2](#step-2-verify-working-in-a-git-repository)): **Scope Hierarchy**: - **Universal** (`/`) - applies everywhere - **Org Level** (`/org/`) - applies to organization - **Repo Level** (`/org/repo/`) - applies to repository - **Path Level** (`/org/repo/path/`) - applies to specific paths --- ## Configuration See `~/.qodo/config.json` for API key setup. Set `QODO_ENVIRONMENT_NAME` env var or `ENVIRONMENT_NAME` in config to select environment. --- ## Common Mistakes - **Re-running when rules are loaded** - Check for "Qodo Rules Loaded" in context first - **Missing compliance comments on ERROR rules** - ERROR rules require a comment documenting compliance - **Forgetting to report when no rules apply** - Always inform the user when no rules were applicable, so they know the rules system is active - **Not in git repo** - Inform the user that a git repository is required and exit gracefully; do not attempt code generation - **No API key** - Inform the user with setup instructions; set `QODO_API_KEY` or create `~/.qodo/config.json` - **No rules found** - Inform the user; set up rules at app.qodo.ai --- Source attribution: sskarz Original project: https://github.com/sskarz/nanoclawbster/blob/798fee5371feaafe2929bdaed7efb9b88a2ea45d/.claude/skills/get-qodo-rules/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Gavriel Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: sskarz Original project: https://github.com/sskarz/nanoclawbster/blob/798fee5371feaafe2929bdaed7efb9b88a2ea45d/.claude/skills/get-qodo-rules/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Product Manager Specialties: API Tools: Qodo Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: a8090ae4e56d91ab80e87186dd48b1ddf679d94871304c06ae11bfe8a7e84806