Agent skill

Get Qodo Rules

Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards.

MITAuto-check: notesDevelopment

Install Get Qodo Rules

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/get-qodo-rules .claude/skills/get-qodo-rules && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .claude/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/get-qodo-rules .agents/skills/get-qodo-rules && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .agents/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/get-qodo-rules .cursor/skills/get-qodo-rules && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .cursor/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sbusso/claudeclaw.git --path skills/get-qodo-rules

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/get-qodo-rules .gemini/skills/get-qodo-rules && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .gemini/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/get-qodo-rules .github/skills/get-qodo-rules && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .github/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sbusso/claudeclaw --skill get-qodo-rules -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sbusso/claudeclaw get-qodo-rules --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/get-qodo-rules .opencode/skills/get-qodo-rules && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "get-qodo-rules" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/get-qodo-rules into .opencode/skills/get-qodo-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-qodo-rules", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: get-qodo-rules
GitHub stars: 194
Token cost: ~1.4k tokens
SKILL.md length: 643 words
Files: 4 (incl. references)
Skills in repo: 23
Repo updated: Aug 12, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards.

Works in 7 steps: Check if Rules Already Loaded → Verify working in a git repository → Verify Qodo Configuration → …
Starting implementation planning
SKILL.md covers Description, Workflow, How Scope Levels Work and Configuration, plus 1 more section
Needs API_KEY and QODO_API_KEY

What it does

Get Qodo Rules is an agent skill from sbusso/claudeclaw. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/output-format.md`, `references/pagination.md` and `references/repository-scope.md`).

It sits in Development, covering Code review and Refactoring. It works with Git. The repository describes itself as: Use Claude to orchestrate agents like OpenClaw. The licence is MIT.

When your agent uses it

Starting implementation planning
Tasks that involve Code review
Tasks that involve Refactoring

Example prompts

“Use the get-qodo-rules skill to load org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification…”
“/get-qodo-rules”

Requirements

A credential in API_KEY
A credential in QODO_API_KEY
Pre-approved tools (allowed-tools): Bash

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Check if Rules Already Loaded
Verify working in a git repository
Verify Qodo Configuration
Fetch Rules with Pagination
Format and Output Rules
Apply Rules by Severity
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 1395af4. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- API_KEY
- QODO_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Get Qodo Rules loads about 1.4k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 643 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~87
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sbusso/claudeclaw at commit 1395af4, republished under its MIT licence (© sbusso). 643 words, ~1,390 tokens.

Download SKILL.mdSave it as .claude/skills/get-qodo-rules/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: get-qodo-rules
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.
allowed-tools: Bash
version: 2.0.0
triggers: get.?qodo.?rules, get.?rules, load.?qodo.?rules, load.?rules, fetch.?qodo.?rules, fetch.?rules, qodo.?rules, coding.?rules, code.?rules, before.?cod…

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 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 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 for the exact format.

Show full SKILL.md (252 more words)Show less

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):

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

Files

SKILL.md and 3 other files (references) in skills/get-qodo-rules of sbusso/claudeclaw.

SKILL.md
references/output-format.md
references/pagination.md
references/repository-scope.md

Open the folder on GitHubat commit 1395af4

Compare with similar skills

Get Qodo Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Get Qodo Rules compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Get Qodo Rules this skillsbusso/claudeclaw	194	—	~1.4k	Automated safety check: Notes	MIT	1 mo ago
Refactortestdouble/han	279	—	~3.1k	Automated safety check: Pass	MIT	7 days ago
Review And Simplify ChangesDimillian/Skills	4k	—	~2k	Automated safety check: Pass	MIT	6 mo ago
Simplify Codetobihagemann/turbo	407	—	~3.5k	Automated safety check: Pass	MIT	yesterday
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	10 days ago
Understand Diff AnalysisEgonex-AI/Understand-Anything	86k	1 repos	~1.4k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Refactor
testdouble/han
Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named…
279 GitHub stars~3.1k tokensUpdated 7 days ago
DevelopmentAuto-check passed
Review And Simplify Changes
Dimillian/Skills
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.
4k GitHub stars~2k tokensUpdated 6 mo ago
DevelopmentAuto-check passed
Simplify Code
tobihagemann/turbo
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes.
407 GitHub stars~3.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
86k GitHub starsUsed in 1 repo~1.4k tokens
DevelopmentAuto-check passed
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
44k GitHub stars~3.1k tokensUpdated 3 days ago
DevelopmentAuto-check passed

Questions about Get Qodo Rules

What does Get Qodo Rules do?

Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Get Qodo Rules is an agent skill from sbusso/claudeclaw. Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards.

When should I use Get Qodo Rules?

Get Qodo Rules fits situations like: starting implementation planning; tasks that involve Code review; tasks that involve Refactoring.

How do I install Get Qodo Rules in Claude Code?

Run `npx skills add sbusso/claudeclaw --skill get-qodo-rules -a claude-code`. Or copy the skill folder (skills/get-qodo-rules in sbusso/claudeclaw) into .claude/skills/get-qodo-rules in your project. Claude Code loads it when a task matches its description.

How do I install Get Qodo Rules in Codex?

Run `npx skills add sbusso/claudeclaw --skill get-qodo-rules -a codex`. Or copy the skill folder (skills/get-qodo-rules in sbusso/claudeclaw) into .agents/skills/get-qodo-rules in your project. Codex loads it when a task matches its description.

Can I use Get Qodo Rules in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sbusso/claudeclaw --skill get-qodo-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/get-qodo-rules, .gemini/skills/get-qodo-rules, .github/skills/get-qodo-rules and .opencode/skills/get-qodo-rules in your project.

What does Get Qodo Rules need to run?

Going by SKILL.md and its folder, Get Qodo Rules needs credentials named API_KEY and QODO_API_KEY. Our summary lists: A credential in API_KEY; A credential in QODO_API_KEY. Its frontmatter pre-approves these tools: Bash.

Does Get Qodo Rules access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Get Qodo Rules safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Get Qodo Rules use?

Get Qodo Rules is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Get Qodo Rules use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 774 tokens, read only when the agent opens those files.

What are the alternatives to Get Qodo Rules?

Skills that share tags, products or a category with Get Qodo Rules: Refactor (testdouble/han, 279 stars), Review And Simplify Changes (Dimillian/Skills, 4k stars), Simplify Code (tobihagemann/turbo, 407 stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Get Qodo Rules?

sbusso (a GitHub user) maintains it in sbusso/claudeclaw, which has 194 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on August 12, 2026.

Source: sbusso/claudeclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Get Qodo Rules

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Get Qodo Rules Skill

Description

Workflow

Step 1: Check if Rules Already Loaded

Step 2: Verify working in a git repository

Step 3: Verify Qodo Configuration

Step 4: Fetch Rules with Pagination

Step 5: Format and Output Rules

Step 6: Apply Rules by Severity

Step 7: Report

How Scope Levels Work

Configuration

Common Mistakes

Files

Compare with similar skills

Similar skills

More from sbusso/claudeclaw

Related

Questions about Get Qodo Rules