Skip to main content

​
Overview

The /get-qodo-rules skill fetches repository-specific coding rules from the Qodo platform API before code generation or modification tasks. It ensures all code changes follow your team’s standards, security requirements, and quality guidelines.
This skill is automatically invoked when you ask Claude to write, edit, refactor, or review code. You typically don’t need to call it manually.

​
When to Use

The skill automatically triggers when:
  • User asks to write, edit, or refactor code
  • Starting implementation planning
  • Building new features
  • Fixing bugs
  • Reviewing code
Skip if: “Qodo Rules Loaded” already appears in conversation context.

​
What It Does

1

Fetches rules from Qodo API

Retrieves:
  • Organization-level coding standards
  • Repository-specific guidelines
  • Security requirements
  • Quality thresholds
  • Team conventions
2

Loads into conversation context

Rules become part of Claude’s context for the current task.
3

Applies during code generation

Claude follows the loaded rules when generating or modifying code.

​
Prerequisites

  • Qodo API key configured in .env: 
    QODO_API_KEY=your-api-key-here
  • Repository registered with Qodo
  • Coding rules configured in Qodo platform

​
How to Apply

Manually invoke (rarely needed): 
/get-qodo-rules
Or let it auto-trigger: 
@Andy implement user authentication
Claude will automatically fetch rules before starting.

​
What Changes

​
Files Modified

  • None (runtime-only skill)

​
Behavioral Changes

  • Code generation follows loaded Qodo rules
  • Security requirements are enforced
  • Quality standards are applied
  • Team conventions are followed

​
Configuration

​
Environment Variables

​
QODO_API_KEY
string
required
API key from Qodo platform
​
QODO_ORG_ID
string
Organization ID (optional, detected from repo)
​
QODO_REPO_ID
string
Repository ID (optional, detected from git remote)

​
Example Rules

Qodo rules might include: 
security:
  - Never log sensitive data
  - Use parameterized queries for SQL
  - Validate all user inputs

quality:
  - Maximum function length: 50 lines
  - Test coverage minimum: 80%
  - No console.log in production code

conventions:
  - Use async/await over callbacks
  - Prefer functional style
  - Export named functions, not default

​
Verification

Check if rules are loaded: 
@Andy what coding rules are you following?
Claude will summarize the loaded Qodo rules.

​
Troubleshooting

Add to .env:
QODO_API_KEY=your-key-here
Get your key from Qodo platform.
Ensure:
  • Repository is registered in Qodo
  • Git remote URL matches Qodo configuration
  • API key has access to the repository
Verify:
  • “Qodo Rules Loaded” appears in conversation
  • Rules are configured in Qodo platform
  • No syntax errors in rule definitions

Qodo PR Resolver

Fix Qodo PR review issues

Customization

Customize NanoClaw behavior

Build docs developers (and LLMs) love

Get started for freeTalk to us