agentmods.dev

gitea-summarize-pull

A pull-request reader that collects the request, its commits, changed files, and discussion, then summarizes the proposed code change and review status.

In plain words
What is it for?
Use it to prepare a review, understand what a pull request changes, check whether it can be merged, and find unresolved questions.
Why use it?
It saves you from reading several parts of a code review separately. It also flags when a long comment thread was only partly loaded.

Skill for Claude CodeCodex

1 9d ago A scan 98 tokens original MIT
View the source file amonstack/gitea_mcp
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/amonstack/gitea_mcp/gitea-summarize-pull
Any agent
npx skills add amonstack/gitea_mcp --skill gitea-summarize-pull
Clone the repo
git clone --depth 1 https://github.com/amonstack/gitea_mcp

Made for: Claude Code, Codex.

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 497 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.00098 $0.00497
Opus 5 $0.00049 $0.00249
Sonnet 5 $0.00020 $0.00099
Haiku 4.5 $0.00010 $0.00050

Measured 2d ago against content hash 67d6f84bbb28, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitea-summarize-pull 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 2d 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.

src/assets/skills/gitea-summarize-pull/SKILL.md · 24 lines

What it actually says

gitea-summarize-pull

Read a pull request and its discussion, then synthesize. Tools: get_pull_request, list_pull_commits, list_pull_files, list_comments.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo).

Flow

  1. get_pull_request({ index }) — index = PR number (URL #N → N), never the internal id. Read title, body, base/head, mergeable, merged, draft, labels, milestone.
  2. list_pull_commits({ index }) — the commit history (page if length === limit).
  3. list_pull_files({ index }) — the diff scope: filenames, statuses, additions/deletions (page if length === limit).
  4. list_comments({ index }) — the review discussion. PR #N == Issue #N — the comment endpoints are shared.

list_comments — TRUNCATION TRAP

  • This tool passes NO page/limit and returns at most the server's default page size. For long review threads the list is SILENTLY TRUNCATED. If the comments count (from get_pull_request) exceeds the number returned, warn that part of the thread is missing and do NOT claim a complete summary.

Synthesis

  • Report: the PR state (open/closed/merged/draft), WHAT it changes (from commits + files), the mergeability/conflict status, then the thread's consensus / decisions / open questions. Attribute by author. Flag unresolved review feedback or blocking questions explicitly — do not paper over disagreement. End with one recommended NEXT ACTION (merge / request changes / close).
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. 2d ago First seen · 24 lines · 98 tokens per session scan A 67d6f84bbb28

Subscribe to this mod's changes

gitea-summarize-pull is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 9d ago), licensed MIT. It adds 98 tokens to every session and 497 once invoked, about $0.0005 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-31.

Code reviewGit and workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens