agentmods.dev

gitea-update-pull

gitea-update-pull is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 135 tokens per session (649 once invoked), scanned A, original, MIT.

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

Written for no agent in particular: nothing here depends on one.

not rated 1repo changed 1mo ago A scan 135 tokens original MIT

Good fit 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.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-update-pull
View source ↗ 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.

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.

Wrote 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.

agentmods badge for gitea-update-pull

README.md
[![agentmods](https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-update-pull/github.svg)](https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-update-pull)
Your own site
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-update-pull"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-update-pull/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.

agentmods 80×15 button for gitea-update-pull

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-update-pull"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-update-pull.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 649 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00135 $0.00649
Opus 5.5 $0.00054 $0.00260
Sonnet 5.5 $0.00027 $0.00130
Haiku 4.5 $0.00014 $0.00065

Measured 1mo ago against content hash 7f53134d3179, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 · 29 lines

What it actually says

gitea-update-pull

When to use

Trigger when the user asks to edit / close / reopen / retarget a PR, or toggle WIP — 中文请求如「关掉这个 PR（不合并）」「把 PR 标成 WIP」「改下目标分支」也 MUST 走本 skill。

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. 1mo ago Changed · +4 lines · +51 tokens per session 7f53134d3179
  2. 1mo 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 21d ago), licensed MIT. It adds 135 tokens to every session and 649 once invoked, about $0.0005 per session on Opus 5.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.

Git and workflowProject management
Related

Other skills, from other repositories

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens

implement-issue

Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.

CopilotKit/OpenTag · 35 tokens