agentleFS
Sign inStart free
hugobatistahugobatista/agent-skills/skills/forge/forgejo-pr/SKILL.md

forgejo-pr

Skill1 starsChanged 55 days agoMITView on GitHub

Create, view, edit, comment, assign, close, merge, search, checkout PRs on a Forgejo repo via fj.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use -p/--pr <ID> if not in the repo directory.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup

fj auth list must show an authenticated session. Pass --repo owner/repo or -R/--remote origin to target a repo.

Create

The branch must already exist on the remote. Find template at .forgejo/pull_request_template.* etc. Fill body under each ## Section heading in /tmp/pr-body.md.

fj pr create --repo owner/repo --head <branch> --base master --body-file /tmp/pr-body.md "<title>"

Flags: --autofill, --web, --agit. Prefix with WIP: for draft.

View

fj pr view <ID>
fj pr view <ID> body
fj pr view <ID> comments
fj pr view <ID> comment <N>
fj pr view <ID> labels
fj pr view <ID> diff
fj pr view <ID> files
fj pr view <ID> commits

Edit

fj pr edit <ID> title "<title>"
fj pr edit <ID> body --body-file <file>
fj pr edit <ID> labels --add <label> --rm <label>
fj pr edit <ID> comment <N> --body-file <file>

Comment

fj pr comment <PR> "<text>"
fj pr comment <PR> --body-file <file>

Assign

fj pr assign <user> [user...]
fj pr unassign <user> [user...]

Use -p/--pr <ID> if not in the repo directory.

Close

fj pr close <ID>
fj pr close -w "reason" <ID>

Merge

fj pr merge <ID> [--method merge|rebase|rebase-merge|squash|manual] [--delete] [--title <t>] [--message <m>]

Search

fj pr search [query] [--labels <l>] [--creator <u>] [--assignee <u>] [--state open|closed|all]

Status

fj pr status <ID> [--wait]

Browse

fj pr browse <ID>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free