Agent skill · magnus919
forgejo-cli
Use when managing a Forgejo or Gitea server from the terminal: issues,
What it needs
About 1k tokens when loaded.
What this skill does
Forgejo CLI v2 Run python3 scripts/forgejo-cli. --agent (default) uses FORGEJOAGENTTOKEN; --user uses FORGEJOUSERTOKEN; --server URL selects an installation. Set FORGEJOSERVER 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 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/forgejo-cli