Borrowing it
Nothing to install: this file belongs to davidruzicka/mcp4openapi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidruzicka/mcp4openapi/main/.claude/skills/use-correct-github-review-comment-enums/SKILL.mdgit clone --depth 1 https://github.com/davidruzicka/mcp4openapiWrote 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/davidruzicka/mcp4openapi/use-correct-github-review-comment-enums)<a href="https://agentmods.dev/skills/davidruzicka/mcp4openapi/use-correct-github-review-comment-enums"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/use-correct-github-review-comment-enums/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/davidruzicka/mcp4openapi/use-correct-github-review-comment-enums"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/use-correct-github-review-comment-enums.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00044 | $0.00358 |
| Opus 5.5 | $0.00018 | $0.00143 |
| Sonnet 5.5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
use-correct-github-review-comment-enums 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 1mo 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.
What it actually says
Goal
Prevent avoidable GitHub MCP tool failures caused by invalid enum values or casing in review-comment payloads.
When to Use
- You call
mcp__github__add_comment_to_pending_review. - You create or submit PR review comments with enum fields such as
subjectTypeorside. - A prior tool call failed with GraphQL validation mentioning enum mismatch.
Rules
- Validate enum fields before sending:
subjectTypemust beLINEorFILE.sideandstartSideshould useLEFTorRIGHTwhen present.
- Prefer
subjectType: LINEfor inline code comments. - Include
pathandlinefor inline comments; usesubjectType: FILEonly for file-level comments. - If a validation error reports enum mismatch, retry once with corrected enum casing/values without changing comment meaning.
- Do not repeat retries beyond one automatic correction attempt.
- Keep review text unchanged while fixing transport/schema fields.
Procedure
- Build comment payload and preflight-check enum fields.
- Send tool call.
- If response contains enum-validation error:
- map invalid enum values to valid constants (
LINE/FILE,LEFT/RIGHT), - resend exactly once.
- Confirm comment presence by reading review comments after successful submission.
Quick Reference
- Correct:
subjectType: "LINE" - Incorrect:
subjectType: "line"
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.
- 1mo ago First seen · 36 lines · 44 tokens per session scan A 27f65b7b5f35
use-correct-github-review-comment-enums is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 358 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…