How do I install the Forgejo CLI skill?

Run npx skillmds@latest add magnus919/forgejo-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forgejo CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forgejo CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forgejo CLI free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Forgejo CLI?

magnus919 (@magnus919) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forgejo CLI by magnus919 — Agent Skill

Name: Forgejo CLI
Rating: 4.2 (5 reviews)
Author: magnus919

Forgejo CLI

Use when managing a Forgejo or Gitea server from the terminal: issues, pull requests, repositories, file contents, labels, milestones, releases, webhooks, user settings, or any /api/v1 endpoint through a safe generic API command. Do not use this skill for unrelated requests; route to the nearest named specialist.

magnus919 Updated Sep 10, 2026

File contents

Forgejo CLI v2

Run python3 scripts/forgejo-cli. --agent (default) uses FORGEJO_AGENT_TOKEN; --user uses FORGEJO_USER_TOKEN; --server URL selects an installation. Set FORGEJO_SERVER in your shell if your wrapper supplies it, otherwise pass --server explicitly.

Safety

Mutations require --force/--yes/-y, or --dry-run.
--dry-run --json emits one plan with method, path, query, and body; it makes no network request.
--json writes exactly one JSON value to stdout; diagnostics go to stderr.
--page and --limit work for any list/search request. Add --include-response to receive the HTTP status plus link and x-total-count pagination headers.
--help does not read credentials or contact a server. Path segments are encoded.

Common workflows

python3 scripts/forgejo-cli issue list --owner acme --repo app --json
python3 scripts/forgejo-cli --dry-run --json repo create --name demo --private
python3 scripts/forgejo-cli --dry-run --json api --method POST \
  --path /api/v1/repos/acme/app/actions/variables --data '{"name":"KEY","value":"value"}'

First-class groups: issue, pr, repo, content, label, milestone, release, hook, and user. content expects base64 and update/delete require the current SHA. Use api for any other /api/v1/ endpoint; it supports JSON, raw files, multipart uploads/forms, and custom headers. Consult /api/swagger or /swagger.v1.json on the selected server. See command reference.

Choosing a command

Use a first-class command for its covered daily workflow. Use api when the operation is absent, requires version-specific fields, or needs a schema not represented by a simple flag. Before using api, read endpoint routing; read API usage for authentication, pagination, compatibility, and safe schema discovery. Read troubleshooting for 401/403/422 responses and transport failures.

---name: forgejo-clidescription: Use when managing a Forgejo or Gitea server from the terminal: issues, pull requests, repositories, file contents, labels, milestones, releases, webhooks, user settings, or any /api/v1 endpoint through a safe generic API command. Do not use this skill for unrelated requests; route to the nearest named specialist.license: MIT---# Forgejo CLI v2Run `python3 scripts/forgejo-cli`. `--agent` (default) uses `FORGEJO_AGENT_TOKEN`; `--user` uses `FORGEJO_USER_TOKEN`; `--server URL` selects an installation. Set `FORGEJO_SERVER` in your shell if your wrapper supplies it, otherwise pass `--server` explicitly.## Safety- Mutations require `--force`/`--yes`/`-y`, or `--dry-run`.- `--dry-run --json` emits one plan with `method`, `path`, `query`, and `body`; it makes no network request.- `--json` writes exactly one JSON value to stdout; diagnostics go to stderr.- `--page` and `--limit` work for any list/search request. Add `--include-response` to receive the HTTP status plus `link` and `x-total-count` pagination headers.- `--help` does not read credentials or contact a server. Path segments are encoded.## Common workflows```bashpython3 scripts/forgejo-cli issue list --owner acme --repo app --jsonpython3 scripts/forgejo-cli --dry-run --json repo create --name demo --privatepython3 scripts/forgejo-cli --dry-run --json api --method POST \ --path /api/v1/repos/acme/app/actions/variables --data '{"name":"KEY","value":"value"}'```First-class groups: `issue`, `pr`, `repo`, `content`, `label`, `milestone`, `release`, `hook`, and `user`. `content` expects base64 and update/delete require the current SHA. Use `api` for any other `/api/v1/` endpoint; it supports JSON, raw files, multipart uploads/forms, and custom headers. Consult `/api/swagger` or `/swagger.v1.json` on the selected server. See [command reference](references/command-reference.md).## Choosing a commandUse a first-class command for its covered daily workflow. Use `api` when the operation is absent, requires version-specific fields, or needs a schema not represented by a simple flag. Before using `api`, read [endpoint routing](references/endpoint-routing.md); read [API usage](references/api-usage.md) for authentication, pagination, compatibility, and safe schema discovery. Read [troubleshooting](references/troubleshooting.md) for 401/403/422 responses and transport failures.

Frequently asked questions