Automated summary
This skill lets an agent manage pull requests in a Forgejo repository through the forgejo-cli command-line tool, using structured JSON actions.
Strengths
- Covers the full PR lifecycle: list, view, create, merge, close and comment
- Explicit JSON input format with a clear table of required parameters per action
- Documented error handling for missing forgejo-cli or invalid repo/PR IDs
- Builds on an existing CLI tool, making it easy to slot into CI/CD pipelines
Limitations
- Assumes forgejo-cli is already installed and configured with valid Forgejo API credentials
- Only targets Forgejo, not GitHub, GitLab or other forges
- Gives no guidance on merge conflicts or branch protection rules
Use it when an agent needs to automate routine pull request operations on a repository hosted on Forgejo.
Avoid it if you work on GitHub or GitLab, or if forgejo-cli is not available in the agent's environment.
Security analysis
CautionThe skill performs legitimate Forgejo PR automation through forgejo-cli, but it requires network access and API credentials and can merge, close, and comment on pull requests. These are powerful remote write actions that could alter repository state if invoked incorrectly. There is no evidence of destructive shell commands, obfuscated payloads, secret exfiltration, or safety-disabling behavior.
- •Uses forgejo-cli with network/API credentials, which may expose tokens if misconfigured or logged
- •Supports write actions that mutate remote repository state: create, merge, close, and comment on PRs
- •The optional `force` merge parameter is not fully defined and could bypass expected merge protections if passed through to the CLI
Examples
List all open pull requests in the repository owner/repo on our Forgejo instance.Open a pull request in owner/repo from branch feature/new-feature into main, titled "Add new feature" with the description "This PR introduces a new feature."Add the comment "Please review the changes." to PR 123 in owner/repo, and then merge it into the target branch.name: manage-pull-requests
description:
A skill for managing pull requests in Forgejo repositories using the forgejo-cli.
Supports creating, listing, viewing, merging, closing, and commenting on PRs.
license: Apache-2.0
compatibility: |
Requires forgejo-cli (https://codeberg.org/forgejo-contrib/forgejo-cli/wiki/PRs).
Agent must have network access to the Forgejo API.
metadata:
category: development-tools
tags: [git, forgejo, pull-requests, automation]
Manage Pull Requests
Overview
This skill enables agents to automate pull request (PR) management in Forgejo repositories using the forgejo-cli tool. It supports common PR operations, making it ideal for CI/CD pipelines, code reviews, and team collaboration workflows.
Instructions
Prerequisites
forgejo-climust be installed and configured with Forgejo API credentials.- The agent must have access to the target repository.
Supported Actions
- List PRs: Fetch all open PRs for a repository.
- View PR: Retrieve details of a specific PR.
- Create PR: Open a new PR from a branch or fork.
- Merge PR: Merge an approved PR into the target branch.
- Close PR: Close a PR without merging.
- Comment on PR: Add or update comments on a PR.
Parameters
Input Format
All actions require a JSON object with the following structure:
{
"action": "<action>",
"repo": "<owner/repo>",
[ "pr_id": "<pr-id>", ]
[ "branch": "<source-branch>", ]
[ "target_branch": "<target-branch>", ]
[ "title": "<pr-title>", ]
[ "description": "<pr-description>", ]
[ "comment": "<comment-text>", ]
[ "force": <boolean> ]
}
Action-Specific Parameters
| Action | Required Parameters | Optional Parameters |
|-----------|----------------------------------------------|-----------------------------------------|
| list | repo | — |
| view | repo, pr_id | — |
| create | repo, branch, title | target_branch, description |
| merge | repo, pr_id | force |
| close | repo, pr_id | — |
| comment | repo, pr_id, comment | — |
Examples
1. List all open PRs
Input:
{
"action": "list",
"repo": "owner/repo"
}
Output: List of open PRs with their IDs, titles, and authors.
2. Create a new PR
Input:
{
"action": "create",
"repo": "owner/repo",
"branch": "feature/new-feature",
"target_branch": "main",
"title": "Add new feature",
"description": "This PR introduces a new feature."
}
Output: Confirmation of PR creation with PR ID.
3. Merge a PR
Input:
{
"action": "merge",
"repo": "owner/repo",
"pr_id": "123",
"force": false
}
Output: Confirmation of merge or error if PR cannot be merged.
4. Add a comment to a PR
Input:
{
"action": "comment",
"repo": "owner/repo",
"pr_id": "123",
"comment": "Please review the changes."
}
Output: Confirmation of comment added.
Error Handling
- If
forgejo-cliis not found:"Error: forgejo-cli is required but not installed. Install it from [forgejo-cli wiki](https://codeberg.org/forgejo-contrib/forgejo-cli/wiki/PRs)." - If the repository or PR ID is invalid:
"Error: Invalid repository or PR ID." - For CLI errors:
Return the raw error message from
forgejo-cli.
References
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/manage-pull-requests-in-forgejo-mrx3xyjc/download' --output '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md.part' && mv '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md.part' '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Environment declared by the author: Requires forgejo-cli (https://codeberg.org/forgejo-contrib/forgejo-cli/wiki/PRs). Agent must have network access to the Forgejo API.
Original excerpt: Prerequisites
forgejo-climust be installed and configured with Forgejo API credentials.- The agent must have access to the target repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && test -s '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/manage-pull-requests' && cp -R '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc' '.claude/skills/manage-pull-requests'Cursor
test -f '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && test -s '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/manage-pull-requests' && cp -R '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc' '.cursor/skills/manage-pull-requests'Codex
test -f '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && test -s '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/manage-pull-requests' && cp -R '.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc' '.agents/skills/manage-pull-requests'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc'openskills read 'manage-pull-requests-in-forgejo-mrx3xyjc'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/manage-pull-requests-in-forgejo-mrx3xyjc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.