qodo-merge
Qodo Merge
Use this skill to install, configure, and troubleshoot Qodo Merge / PR-Agent without pulling large chunks of product docs into the active context.
Start here
- Identify the platform: GitHub Action/App, GitLab, Bitbucket, Azure DevOps, Docker, AWS Lambda, or self-hosted.
- Identify the job: install, configure, use a tool command, switch models, or debug a failure.
- Prefer repo-local
.pr_agent.tomlfor stable settings and env vars only for secrets or one-off overrides. - Read only the reference file that matches the task instead of loading everything.
Core commands
| Command | Use it for |
|---|---|
/describe |
Generate PR title, summary, walkthrough, labels, and optional diagram |
/review |
Review the PR for quality, correctness, security, and ticket alignment |
/improve |
Generate inline code suggestions and rank them by confidence |
/ask "..." |
Ask questions about the diff, files, or intent of the PR |
/add_docs |
Add missing docs for changed code |
/generate_labels |
Infer labels from PR content |
/help_docs "..." |
Answer repo questions from project documentation |
High-value rules
- Config precedence is: CLI args -> env vars ->
.pr_agent.toml-> defaults. - For env var overrides, config keys map with double underscores, for example
PR_REVIEWER__REQUIRE_TESTS_REVIEW=false. - AWS Lambda env vars cannot contain
.; use__instead. - Non-OpenAI providers use their own API keys. Do not require
OPENAI_KEYfor Claude, Gemini, or similar providers. suggestions_score_thresholdcontrols how aggressive/improveis; raise it to reduce low-value suggestions.allow_dynamic_context = truehelps larger diffs by expanding surrounding code context.- Use description markers when the user wants generated PR bodies to fit a repo template cleanly.
- Local Ollama setups generally require a self-hosted runner; hosted CI cannot reach local services.
Troubleshooting shortcuts
| Symptom | First check |
|---|---|
| Model not found | Provider-specific model name format |
| API key missing | Matching secret/env var name for the selected provider |
| Permission denied | PR, issue, and contents write permissions in the integration |
| Bad JSON in provider config | litellm.extra_body formatting |
| Weak context on large PRs | Dynamic context and patch sizing settings |
Routing guide
- Installation and platform-specific setup:
references/installation.md - Tool behavior and per-tool config:
references/tools.md .pr_agent.toml, CLI flags, env vars, model wiring:references/usage-guide.md- Self-reflection, compression, dynamic context, metadata:
references/core-abilities.md - Product overview, FAQ, and miscellaneous details:
references/other.md - Mirrored documentation index:
references/documentation/index.md
Working style
- Keep answers implementation-focused: pick the right platform path, show the minimal config, and explain only the options that matter to the user's case.
- Avoid dumping long examples from docs unless the user needs a ready-to-paste workflow or config block.
- Treat https://qodo-merge-docs.qodo.ai/ as the source of truth for exact option names and current behavior.
More from aaronflorey/agent-skills
amber-lang
Write, debug, and explain Amber code, the `amber` language that compiles `.ab` files to Bash. Use this skill when the user asks to write an Amber script, convert Bash to Amber, compile Amber to Bash, debug Amber syntax or type errors, or asks about Amber 0.5.1-alpha syntax, functions, types, error handling, the standard library, or the `amber` CLI.
26go-cobra
Write, scaffold, and debug Go CLI applications with `github.com/spf13/cobra`. Use this skill whenever the user mentions Cobra, `cobra.Command`, a Go command-line app, subcommands, persistent or local flags, required flags, argument validation, shell completions, generated docs, or wants to build or refactor a cobra-based CLI.
24laravel-actions
Write, scaffold, explain, and refactor code using the `lorisleiva/laravel-actions` package. Use this skill whenever the user mentions Laravel Actions, `AsAction`, `php artisan make:action`, action classes, converting a controller, job, listener, or command into an action, dispatching an action as a job, using an action as a controller or listener, or adding validation, authorization, testing, or mocking around an action.
24num30-config
Write, debug, and explain Go configuration code using `github.com/num30/config`. Use this skill when the user mentions `num30/config`, wants config structs, file plus env plus CLI flag loading, validation, config watching, precedence rules, or asks how to integrate the num30/config package into a Go application.
22pelican-panel-plugins
Write, scaffold, explain, and debug plugins for the Pelican gaming panel. Use this skill whenever the user mentions Pelican plugins, extending Pelican, FilamentPHP resources or pages for Pelican, plugin service providers, custom permissions, plugin settings, routes, models, widgets, or asks how to add new functionality to the Pelican panel.
21go-viper
Write, debug, and explain Go configuration code with `github.com/spf13/viper`. Use this skill whenever the user mentions Viper, `viper`, config structs, reading config from files plus env vars plus flags, Cobra or `pflag` integration, unmarshaling into structs, env key replacers, config precedence, config watching, or a clean Viper bootstrap.
20