get-qodo-rules

Fetches org- and repo-level coding rules from the Qodo API before code generation tasks.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill get-qodo-rules-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-qodo-rules
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/get-qodo-rules
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill get-qodo-rules-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams define coding standards, security requirements, and quality guidelines in Qodo, but AI-generated code often ignores them because the rules are never loaded into context. This Skill retrieves those rules automatically before any code is written, edited, or reviewed. ## Core Features & Use Cases - Scoped Rule Retrieval: Detects repository and module-level scope from the git remote URL and fetches matching universal, org, repo, and path-level rules from the Qodo platform API. - Severity-Based Enforcement: Groups rules into ERROR, WARNING, and RECOMMENDATION tiers, requiring compliance comments for ERROR rules and explanations when WARNING rules are skipped. - Paginated Fetching with Error Handling: Retrieves all rule pages (50 per page, up to 100 pages) and handles HTTP errors such as 401, 403, 429, and 5xx gracefully. - Use Case: Before implementing a new feature in a monorepo module, the Skill loads the team's Qodo rules for that module path, then the generated code includes compliance comments for mandatory security rules. ## Quick Start Ask the assistant to load Qodo rules before writing or refactoring code in your git repository.

Frequently Asked Questions about get-qodo-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load Qodo coding rules before generating code?

Invoke the Skill before any code generation or modification task. It reads your API key from ~/.qodo/config.json, detects the repository scope from the git origin remote, fetches all active rules from the Qodo API, and prints them grouped by severity.

How does Qodo rule scoping work for monorepo modules?

The Skill parses the git remote URL into an /org/repo/ scope, and if the working directory is inside a modules/* subdirectory, it uses that path as the query scope. The API returns universal, org, repo, and path-level rules matching that prefix.

What happens if no Qodo API key is configured?

The Skill checks ~/.qodo/config.json for the API_KEY field and exits gracefully with setup instructions if it is missing. The QODO_ENVIRONMENT_NAME environment variable can override the ENVIRONMENT_NAME config field.

Why does the Qodo rules fetch return a 401 or 404 error?

A 401 means the API key is invalid or expired, while a 404 usually indicates a wrong environment name in QODO_ENVIRONMENT_NAME. The Skill reports each HTTP error type with a user-friendly message and exits gracefully.

When should I skip loading Qodo rules?

Skip loading when "Qodo Rules Loaded" already appears in the conversation context, since re-fetching is redundant. Also note the Skill requires a git repository with a parseable origin remote; outside a repo it exits without fetching.