skills.rest
dismantl
dismantlCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

forgejo-pr

Manage Forgejo and Gitea pull requests via MCP tools.

Updated Jun 8, 2026
Search Tags:#git#code review#mcp#pull requests#pr management#gitea#forgejo
One-click install
npx skills add https://github.com/dismantl/agent-skills --skill forgejo-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forgejo-pr
Source: https://github.com/dismantl/agent-skills/tree/main/skills/forgejo-pr
Command: npx skills add https://github.com/dismantl/agent-skills --skill forgejo-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually managing pull requests on self-hosted Forgejo or Gitea instances requires switching between tools, writing custom API calls, and handling authentication manually, which is time-consuming and error-prone. This skill automates the full pull request lifecycle using native, authenticated MCP tools.

Core Features & Use Cases

  • Full PR Lifecycle Management: List, view, comment on, create, merge, and close pull requests directly via official Forgejo MCP tools.
  • Safe PR Checkout: Automatically handle checkout for both same-repo and forked pull requests using metadata from the PR itself.
  • Use Case: If your team uses a self-hosted Forgejo instance for code review, use this skill to quickly list all open PRs, review diffs, leave threaded feedback, and merge approved changes without writing custom curl commands or handling API tokens manually.

Quick Start

Use the forgejo-pr skill to list all open pull requests for the current repository and summarize their titles, authors, and merge status.

Frequently Asked Questions about forgejo-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Forgejo pull requests without writing custom API calls?▼

Managing Forgejo pull requests without custom API calls is automated natively through MCP tooling to list, view, comment, create, merge, and close PRs. This eliminates manual token handling and curl commands.

Can I check out pull request branches locally from forked Gitea repositories?▼

Checking out pull request branches locally from forked Gitea repositories is supported using metadata from the PR itself. The checkout process handles both same-repo and forked PR branches automatically.

What is the safest way to merge Forgejo pull requests via MCP?▼

The safest way to merge Forgejo pull requests via MCP involves built-in safety guardrails that enforce mandatory MCP usage and require explicit user confirmation for destructive actions like merging or closing.

Does this MCP pull request management skill work with both Gitea and Forgejo?▼

This MCP pull request management skill works with both Gitea and Forgejo. It automates the full pull request lifecycle for self-hosted instances using native, authenticated MCP tools without manual authentication.

Why does my Gitea pull request API call return a 404 error?▼

A Gitea pull request API call returning a 404 error is addressed by built-in troubleshooting for common authentication and 404 issues. The skill enforces strict safety guardrails to prevent these common errors.

How do I list all open pull requests on a self-hosted Forgejo instance?▼

Listing all open pull requests on a self-hosted Forgejo instance is done by using native MCP tools to retrieve and summarize PR titles, authors, and merge status directly without manual API configuration.

Related Skills

Explore More Software Engineering Skills→
L3DigitalNetL3DigitalNet
6

gitea

Manage Gitea and Forgejo Git services across native and Docker deployments.

Official
Advanced
cryptopaficryptopafi

github-code-review

Review git diffs and GitHub pull requests with structured feedback.

Community
Intermediate
Lutra23Lutra23

github-pr

Fetch, preview, merge, and test GitHub pull requests locally.

Community
Advanced
mnishanth02mnishanth02

clerk-backend-api

Access Clerk REST API endpoints to list users and manage organizations.

Community
Basic