developer_pr_prep

A workflow for preparing a GitHub pull request, which is a proposed set of code changes for review and merging. It checks the branch and diff, runs relevant tests, and drafts the request text.

In plain words
What is it for?
Use it to prepare branches, review changed files, verify tests, write a pull request summary, and explicitly approve pushing or opening the request.
Why use it?
It catches branch, test, and review details before changes are pushed or a pull request is opened.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/siddsachar/row-bot/developer_pr_prep
Any agent
npx skills add siddsachar/row-bot --skill developer_pr_prep
Clone the repo
git clone --depth 1 https://github.com/siddsachar/row-bot

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00218
Opus 5 $0.00011 $0.00109
Sonnet 5 $0.00004 $0.00044
Haiku 4.5 $0.00002 $0.00022

Measured yesterday against content hash 3d6541646533, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

developer_pr_prep 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 yesterday.

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.

bundled_skills/developer_pr_prep/SKILL.md · 31 lines

What it actually says

Developer PR Prep

Use this skill when the user wants to prepare, push, or open a pull request from Developer Studio.

Workflow:

  1. Check workspace identity, branch, remote, dirty state, and GitHub CLI status.
  2. Recommend a feature branch when the user is still on a protected or shared branch.
  3. Review the diff and line counts.
  4. Run the relevant tests or clearly state why they were not run.
  5. Draft a PR title/body with summary, changed files, tests, and risk.
  6. Treat push and PR creation as explicit user-approved actions.

If GitHub CLI is missing or unauthenticated, explain the shortest install/auth path for the current platform.

Changes

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.

  1. yesterday First seen · 31 lines · 22 tokens per session scan A 3d6541646533

Subscribe to this mod's changes

developer_pr_prep is a skill published in the GitHub repository siddsachar/row-bot (1,474 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 218 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

rich-post

Send a Telegram rich-media post to ANOTHER allowlisted chat via the bot (Bot API 10.1 sendRichMessage) - text, inline images, tables, headings, lists, quotes, collapsible blocks, formulas, collages/slideshows ALL in one message bubble. Use when the owner asks to post somewhere other than the current conversation (the…

smixs/iva-agent · 129 tokens

telegram-userbot

Подключение и работа с личным Telegram-аккаунтом владельца (userbot, НЕ бот). Используй, когда просят читать личные чаты/переписку/диалоги, искать по своим сообщениям, писать кому-то от своего имени, «зайди в мой телеграм», «подключи мой телеграм», «прочитай личку», «ответь в личке», «перешли сообщение», а также при…

smixs/iva-agent · 144 tokens

memory-processor

Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…

smixs/iva-agent · 106 tokens

code-review-github

GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.

initializ/forge · 30 tokens

agent-browser

Браузерная автоматизация для интерактивных веб-задач. Используй, когда нужно открыть сайт, заполнить форму, кликнуть, сделать скриншот, залогиниться, спарсить JS-страницу или протестировать веб-приложение. Триггеры — «зайди на сайт», «заполни форму», «нажми кнопку», «скриншот страницы», «войди в аккаунт», «спарси…

smixs/iva-agent · 114 tokens

update-recovery

Restore or merge user customizations preserved during an Iva update. Use when the owner says "restore my update changes", "recover my customizations", «верни мои изменения после обновления», «восстанови мои доработки» or asks about an update conflict.

smixs/iva-agent · 60 tokens