Apache Doris Skills is a collection of agent instructions containing Apache Doris database knowledge for designing, sizing, operating, diagnosing, and contributing to Doris clusters. It serves developers and operators using Claude Code, Cursor, Codex, Cline, Amp, and other agent tools, with the skills providing decision logic and evidence-based workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add apache/doris-skills --skill doris-repo-reviewgit clone --depth 1 https://github.com/apache/doris-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/apache/doris-skills/doris-repo-review)<a href="https://agentmods.dev/skills/apache/doris-skills/doris-repo-review"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/doris-repo-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apache/doris-skills/doris-repo-review"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/doris-repo-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 251 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 237 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 239 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00180 | $0.09290 |
| Opus 5 | $0.00090 | $0.04645 |
| Sonnet 5 | $0.00036 | $0.01858 |
| Haiku 4.5 | $0.00018 | $0.00929 |
Grade A, and why
doris-repo-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local pipeline-style Doris code review
This skill reviews a Pull Request against a local clone of the Apache Doris source repository. It is a contributor-side workflow, not a cluster-operations skill: it never talks to a running cluster and never needs one.
Usage:
/doris-repo-review https://github.com/apache/doris/pull/66807
/doris-repo-review https://github.com/apache/doris/pull/66807 focus on class loading and compatibility
/doris-repo-review 66807 # a bare number defaults to apache/doris
This ports the review flow of apache/doris/.github/workflows/code-review-runner.yml to a local
machine: first align the current directory to the PR head, take the diff from local git, and
produce one English and one Chinese document under the current directory's review-docs/.
Everything else - required reading, main-agent risk scan, subagent split, shared ledger, at most
3 convergence rounds, an explicit conclusion per checkpoint - matches CI.
The scope is the one worktree you are standing in. No other worktree is scanned, chosen, or created; no environment variable selects a different directory; nothing is assumed about the machine's directory layout.
Let $S be this skill's own scripts/ directory (with a default Claude Code install that is
~/.claude/skills/doris-repo-review/scripts):
$S/align-to-pr.sh <PR> --check # diagnosis only, changes nothing
$S/align-to-pr.sh <PR> --out "$CTX/align.env" # step 1: align the current directory
$S/prepare-review-context.sh --ctx "$CTX" --align "$CTX/align.env" # step 2: gather context
$S/coverage-report.sh --ctx "$CTX" # step 6a: what has nobody read yet
python3 $S/verify-review-docs.py --ctx "$CTX" --doc <en> --doc <zh> # step 9: verify documents
$S/record-review-runtime.sh --ctx "$CTX" --model <id> --effort <effort>
$S/post-pass-comment.sh --ctx "$CTX" # step 10: auto-post PASS
$S/review-runtime-policy.sh check <model> <effort> # reviewer eligibility
$S/save-run-state.sh --ctx "$CTX" --verdict ... --findings b,m,mi,n # step 11: leave state for next time
| File | Purpose |
|---|---|
scripts/align-to-pr.sh |
Resolve the PR, diagnose how the current directory relates to it, align it to the PR head |
scripts/prepare-review-context.sh |
Produce the authoritative diff, new-side line ranges, required AGENTS.md list, existing comments, ledger skeleton |
scripts/coverage-report.sh |
Mechanical check of which changed files no ledger file has mentioned yet |
scripts/verify-review-docs.py |
Validate commit, anchors, EN/ZH agreement, verdict, findings, rounds, and convergence |
scripts/record-review-runtime.sh |
Record the qualified reviewer model, effort, and exact commit |
scripts/review-runtime-policy.sh |
The exact model and effort allowlist for a pipeline-equivalent review |
scripts/post-pass-comment.sh |
Render and post the machine-readable PASS comment; refuses everything that is not a pass |
scripts/save-run-state.sh |
Persist this run's merged ledger under the stable per-PR state directory, so the next review inherits its dismissals |
references/prompts.md |
Subagent prompt templates (CI wording, carried over verbatim) |
references/doc-templates.md |
Templates for both documents, anchor format, verdict rule |
references/pr-comment-format.md |
The doris-repo-review/v1 comment schema, field meanings, and how a program reads it back |
references/qualified-runtime.md |
How to select or delegate to a qualified lead and coverage reviewers |
Requirements: git, an authenticated gh CLI, jq, and python3. The clone must have full
history (git fetch --unshallow on a shallow one), because the authoritative diff is a three-dot
diff from the merge base.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/doc-templates.md 10.0 KB
- references/pr-comment-format.md 5.7 KB
- references/prompts.md 12 KB
- references/qualified-runtime.md 2.3 KB
- scripts/align-to-pr.sh 9.9 KB runs code
- scripts/coverage-report.sh 4.1 KB runs code
- scripts/post-pass-comment.sh 11 KB runs code
- scripts/prepare-review-context.sh 19 KB runs code
- scripts/record-review-runtime.sh 1.7 KB runs code
- scripts/review-runtime-policy.sh 1.6 KB runs code
- scripts/save-run-state.sh 3.9 KB runs code
- scripts/verify-review-docs.py 12 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago Changed · +3 tokens per session 2181c9ce4c6a
- 8d ago Changed · -5 lines · -136 tokens per session 3388dc1e0800
- 12d ago First seen · 634 lines · 313 tokens per session scan A e2180c83a245
doris-repo-review is a skill published in the GitHub repository apache/doris-skills (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 180 tokens to every session and 9,290 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
issue-work-loop
Run Herdr loops for one open GitHub issue (resolve→review→fix) or an existing PR (review→lazy fixer) until CLEAN. Don't use for plain resolution without review, review-only/no-fix requests, backlog automation, or merging.
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch/PR policies, CLI/IDE integrations, CodeQL/scanning, or…
hashiiiii-pull-request
Use this skill to create or edit a GitHub pull request with the repository template or the default structure.
cf-ship-custom
This is a version bump + ship + release operation. Run these steps BEFORE the standard cf-ship workflow.