Borrowing it
Nothing to install: this file belongs to priyanshuchawda/tracepilot-gemini-cli. 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/priyanshuchawda/tracepilot-gemini-cli/main/.gemini/skills/pr-address-comments/SKILL.mdgit clone --depth 1 https://github.com/priyanshuchawda/tracepilot-gemini-cliWrote 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/priyanshuchawda/tracepilot-gemini-cli/pr-address-comments)<a href="https://agentmods.dev/skills/priyanshuchawda/tracepilot-gemini-cli/pr-address-comments"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/pr-address-comments/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/priyanshuchawda/tracepilot-gemini-cli/pr-address-comments"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/pr-address-comments.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.00036 | $0.00227 |
| Opus 5 | $0.00018 | $0.00113 |
| Sonnet 5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
pr-address-comments 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 9d 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.
This is a copy
100% identical to pr-address-comments — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are helping the user address comments on their Pull Request. These comments may have come from an automated review agent or a team member.
OBJECTIVE: Help the user review and address comments on their PR.
Comment Review Procedure
- Run the
scripts/fetch-pr-info.jsscript to get PR info and state. MAKE SURE you read the entire output of the command, even if it gets truncated. - Summarize the review status by analyzing the diff, commit log, and comments to see which still need to be addressed. Pay attention to the current user's comments. For resolved threads, summarize as a single line with a ✅. For open threads, provide a reference number e.g. [1] and the comment content.
- Present your summary of the feedback and current state and allow the user to guide you as to what to fix/address/skip. DO NOT begin fixing issues automatically.
What ships with it
1 file 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.
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.
- 9d ago First seen · 14 lines · 36 tokens per session scan A 96ffbdccdbc2
pr-address-comments is a skill published in the GitHub repository priyanshuchawda/tracepilot-gemini-cli (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 227 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pr-address-comments, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
gitlab-create-mr
Create GitLab merge requests from a local branch using a reviewable workflow for branch checks, GitLab host detection, diff analysis, title and description writing, and glab mr create. Use when opening a GitLab merge request, drafting or improving merge request copy, preparing a branch for review, or working across…
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
code-review
Request or perform a git-backed code review for a defined diff or SHA range using implementation context and requirements. Use when finishing a task, completing a major feature, preparing to merge, or when you need a fresh review before proceeding.