Borrowing it
Nothing to install: this file belongs to hrygo/hotplex-legacy. 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/hrygo/hotplex-legacy/main/.agent/skills/hotplex-pr-master/SKILL.mdgit clone --depth 1 https://github.com/hrygo/hotplex-legacyWrote 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/hrygo/hotplex-legacy/hotplex-pr-master)<a href="https://agentmods.dev/skills/hrygo/hotplex-legacy/hotplex-pr-master"><img src="https://agentmods.dev/badge/skills/hrygo/hotplex-legacy/hotplex-pr-master.svg" alt="Measured on agentmods" 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.00124 | $0.03950 |
| Opus 5 | $0.00062 | $0.01975 |
| Sonnet 5 | $0.00025 | $0.00790 |
| Haiku 4.5 | $0.00012 | $0.00395 |
Grade A, and why
hotplex-pr-master 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 6d 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HotPlex PR 管理大师 🚀
全方位 GitHub Pull Request 智能管理工具，基于大型开源项目（Kubernetes, React, VS Code）的最佳实践，为 HotPlex 提供企业级 PR 管理能力。
核心能力
0. 智能自适应与增量管理 🧠 [核心优势]
只对当下必须要进行管理的对象进行管理，大幅提升效率：
增量管理 (Incremental Management)
- 状态缓存 - 记录已处理 PRs 的状态，避免重复处理
- 变化检测 - 只处理有更新的 PRs（since last_check）
- 智能同步 - 支持
--since参数增量更新 - 去重机制 - 避免重复打标签、重复评论
智能优先级判断 (Smart Prioritization)
自动识别需要立即关注的 PRs：
- ✅ 立即处理：P0/P1 优先级、CI 失败、冲突、长期未 review
- ⏸️ 延迟处理：P2/P3 优先级、Draft、Stale PRs
- 🔄 定期批量处理：每周日处理 low priority PRs
自适应策略 (Adaptive Strategy)
根据项目状态动态调整管理策略：
if open_prs < 10:
strategy = "comprehensive" # 全面管理所有 PRs
elif open_prs < 50:
strategy = "focused" # 只管理高优先级和有问题 PRs
else:
strategy = "essential" # 只管理 P0/P1 和阻塞 PRs
智能触发条件 (Smart Triggers)
只在以下情况介入管理：
- PR 状态变更（opened/synchronize/review_requested）
- CI 状态变化（success → failure）
- 冲突出现
- 长期未 review（7+ 天）
- 优先级提升（P3 → P1）
管理效率提升
- 减少 API 调用：增量更新降低 80% API 调用
- 节省时间：只处理必要 PRs，减少 60% 处理时间
- 智能批处理：低优先级 PRs 批量处理，减少打扰
使用示例：
# 增量更新 - 只处理过去 24 小时有更新的 PRs
"增量更新 PRs --since 24h"
# 只管理需要关注的 PRs
"智能管理高优先级和阻塞 PRs"
# 清理模式 - 只处理 stale PRs
"清理超过 30 天的 stale PRs"
1. 自动标注 (Auto-Labeling)
自动分析并应用 7 维度标签：
- 优先级：
priority/critical,priority/high,priority/medium,priority/low - 类型：
type/bug,type/feature,type/enhancement,type/docs,type/test,type/refactor,type/security - 规模：
size/small,size/medium,size/large - 状态：
status/draft,status/ready-for-review,status/review-requested,status/approved,status/blocked - Review：
review/changes-requested,review/approved,review/pending - 平台：
platform/slack,platform/telegram,platform/feishu,platform/discord - 模块：
area/engine,area/adapter,area/provider,area/security,area/admin,area/brain
2. 生命周期管理 (Lifecycle Management)
- 自动检测 PR 状态（Draft → Ready → Review → Approved → Merged）
- 冲突自动检测与标注
- CI/CD 状态监控与阻塞提醒
- 长期未更新 PR 自动提醒（30+ 天）
What ships with it
5 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.
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.
- 6d ago First seen · 413 lines · 124 tokens per session scan A f51a964ec2c0
hotplex-pr-master is a skill published in the GitHub repository hrygo/hotplex-legacy (11 stars, last pushed 4mo ago), licensed MIT. It adds 124 tokens to every session and 3,950 once invoked, about $0.0006 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
bmad-loop
Iterate over a list of story keys, executing dev → review → PR → CI → merge for each. Use when the user says "loop these stories [list]" or "run the loop on [story keys]".
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…