forgejo-cli

Manage Forgejo repositories, issues, pull requests, and releases via the tea CLI.

6|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/Xipher-Labs/walter-os --skill forgejo-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forgejo-cli
Source: https://github.com/Xipher-Labs/walter-os/tree/main/skills/forgejo-cli
Command: npx skills add https://github.com/Xipher-Labs/walter-os --skill forgejo-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes manual, error-prone Forgejo administration by giving operators a reliable way to create and manage repositories, issues, pull requests, and releases against the self-hosted Forgejo instance using the official tea CLI.

Core Features & Use Cases

  • Repository operations: list, create, and clone Forgejo repositories (including private repos) as part of daily development workflows.
  • Issue management: create, comment on, list, and close issues tied to specific project work.
  • Pull request workflows: list PRs, open/check out PRs locally, and merge PRs with the required approval discipline.
  • Release publishing: create and list tagged releases with notes/changelog text.

Quick Start

Use the forgejo-cli skill to create a private repository and open follow-up work by running: “Create a private Forgejo repo named foo, then list issues for it on git.${WALTER_DOMAIN}.”

Frequently Asked Questions about forgejo-cli

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

FAQPage Schema
How do I manage Forgejo repositories and issues using the tea CLI?

You can manage Forgejo repositories and issues using the official tea CLI by creating repos, opening issues, and coordinating pull requests directly on your self-hosted git instance. This replaces unmaintained MCPs with a reliable command-line workflow.

What is the best way to automate Forgejo release publishing from the command line?

The best way to automate Forgejo release publishing is using the tea CLI to create and list tagged releases with notes and changelog text. This provides reliable release automation without relying on unmaintained MCP tools.

Do I need a specific token to interact with a self-hosted Forgejo instance via CLI?

Yes, you need a configured tea login using a scoped FORGEJO_TOKEN to interact with a self-hosted Forgejo instance. This token authenticates your CLI session for repo management, issue tracking, and pull request workflows.

Can I check out and merge pull requests locally using the tea CLI for Forgejo?

Yes, you can list, open, and check out pull requests locally using the tea CLI for Forgejo. It supports PR workflows with required approval discipline, allowing you to coordinate merges safely on your self-hosted instance.

What are the limitations when managing Forgejo repos with the tea CLI?

Limitations of managing Forgejo repos with the tea CLI include following operational safety rules like using PRs instead of pushing directly to main and avoiding any automated repo deletion to prevent accidental data loss.