agentmods.dev

gitea-update-pull

A tool for editing one existing Gitea pull request, including its fields and open or closed state. Gitea is a service for hosting code repositories and reviewing proposed changes.

In plain words
What is it for?
Use it to edit pull request details, close or reopen a request, mark it as work in progress, change its target branch, or update its assignees and milestone.
Why use it?
It reduces mistakes when changing a pull request by requiring the current state to be read first and by keeping actions such as closing separate from merging.

Skill for Claude CodeCodex

1 9d ago A scan 84 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-update-pull
Any agent
npx skills add amonstack/gitea_mcp --skill gitea-update-pull
Clone the repo
git clone --depth 1 https://github.com/amonstack/gitea_mcp

Made for: Claude Code, Codex.

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 533 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.00084 $0.00533
Opus 5 $0.00042 $0.00267
Sonnet 5 $0.00017 $0.00107
Haiku 4.5 $0.00008 $0.00053

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

Security

Grade A, and why

gitea-update-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-update-pull/SKILL.md · 25 lines

What it actually says

gitea-update-pull

Edit one pull request's fields or change its state. Tools: get_pull_request, update_pull_request.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo).
  • There is NO optimistic locking — always read current state first.

Flow

  1. READ CURRENT: get_pull_request({ index }) — index = PR number (URL #N → N), never the internal id.
  2. APPLY: update_pull_request({ index, ...changedFields }).

update_pull_request

  • RULES: PATCH — only fields you pass change; omit = unchanged. To CLEAR a field pass its EMPTY form, do NOT omit it: milestone: 0 clears the milestone, assignees: [] clears assignees. Use assignees (array), not the deprecated assignee. State values are open | closed.
  • CLOSE WITHOUT MERGING: update_pull_request({ index, state: "closed" }). This closes the PR but does NOT merge it — the commits stay on the head branch. Reopen later with state: "open".
  • WIP TOGGLE: to mark work-in-progress, prefix the title with WIP: or [WIP]. To mark ready, remove the prefix. Pass the full new title.
  • RETARGET: base changes the target branch. RARELY REVERSIBLE — confirm with the user before retargeting; it can invalidate reviews and conflict checks.
  • NOT FOR single-label changes: labels here are IDs and REPLACE the entire set — to add/remove one label use add_issue_labels / remove_issue_label (gitea-label-issue, PR #N == Issue #N).
  • CHECK FIRST: get_pull_request for current values if state may have changed since your last read; state the intended change to the user before writing.
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 · 25 lines · 84 tokens per session scan A 3634013abbbd

Subscribe to this mod's changes

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

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

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 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