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.
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
If rules are already loaded (look for "Qodo Rules Loaded" in recent messages), skip to step 6.
origin remote URL. If no remote is found, exit silently. If the URL cannot be parsed, inform the user and exit gracefully.modules/* subdirectory, use it as the query scope; otherwise use repository-wide scope.See repository scope detection for details.
Check that the required Qodo configuration is present. The default location is ~/.qodo/config.json.
~/.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.~/.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.See pagination details for the full algorithm and error handling.
- **{name}** ({category}): {description}---.See output format details for the exact format.
| 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 |
After code generation, inform the user about rule application:
Determines scope from git remote and working directory (see Step 2):
Scope Hierarchy:
/) - applies everywhere/org/) - applies to organization/org/repo/) - applies to repository/org/repo/path/) - applies to specific pathsSee ~/.qodo/config.json for API key setup. Set QODO_ENVIRONMENT_NAME env var or ENVIRONMENT_NAME in config to select environment.
QODO_API_KEY or create ~/.qodo/config.json