get-qodo-rules

Load repository-specific coding rules from the Qodo platform API.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill get-qodo-rules-spyqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-qodo-rules
Source: https://github.com/spyqs/nanoclaw-email-imap/tree/main/.claude/skills/get-qodo-rules
Command: npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill get-qodo-rules-spyqs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It ensures that code generation and changes follow your team’s established security, quality, and style rules from Qodo, so you don’t drift from standards during implementation.

Core Features & Use Cases

  • Repository-scoped rules loading: Detects scope from your git remote (and uses module-level scope when inside modules/*) to fetch the correct org/repo/path rules.
  • Qodo API rule retrieval with pagination: Loads active rules across pages (up to a safety limit) and handles common API error conditions gracefully.
  • Severity-based enforcement guidance: Groups rules into ERROR, WARNING, and RECOMMENDATION, then instructs how to comply or report when rules are skipped.
  • Pre-coding workflow support: Helps you use the rules before writing, editing, refactoring, or reviewing code, especially when rules are not yet present in the conversation.

Quick Start

Use get-qodo-rules in your Claude Code session before asking it to write, edit, refactor, or review code in a 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 team coding standards before generating code in a git repository?

Load team coding standards by fetching repository-specific rules from the Qodo platform API before code generation begins. It detects scope from your git remote and retrieves active rules via paginated GET requests.

How do I enforce Qodo security rules during code refactoring?

Enforce Qodo security rules during refactoring by fetching active rules and grouping them by severity. It provides ERROR, WARNING, and RECOMMENDATION compliance guidance to prevent drifting from established standards.

Can I apply module-level scoping when fetching coding standards from a Qodo repository?

Yes, module-level scoping is supported when working inside `modules/*` directories. It fetches the correct org, repo, and path rules based on your current location within the repository structure.

What configuration do I need to retrieve active rules from the Qodo API?

Retrieving active rules from the Qodo API requires reading configuration from `~/.qodo/config.json`. This file must contain your API key and environment name to authenticate paginated GET requests successfully.

How are coding standards formatted when loaded from the Qodo platform?

Coding standards are formatted by severity level when loaded from the Qodo platform. Rules are grouped into ERROR, WARNING, and RECOMMENDATION categories, instructing how to comply or report when rules are skipped.

Why does code generation drift from established security and quality rules?

Code generation drifts from standards when team rules are not loaded into the conversation context beforehand. Loading repository-specific Qodo rules before writing or editing code ensures compliance with established security and quality guidelines.