gitea

What This Skill Does

The Gitea skill provides a robust interface for the OpenClaw AI agent to interact with Gitea instances using the tea CLI. It enables comprehensive repository management, pull request handling, issue tracking, and CI/CD orchestration. By acting as a bridge between the agent and the Gitea API, it allows for automated workflows such as creating issues based on logs, managing releases, setting up webhooks, and monitoring repository health without leaving the terminal or the agent environment.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ericxliu1990/gitea Once installed, ensure you have the tea CLI installed on your system. Run tea login add to authenticate with your preferred Gitea instance and verify your identity with tea whoami.

Use Cases

This skill is perfect for DevOps engineers and developers who need to streamline their git-based workflows. You can use it to automate the creation of bug reports from error logs, manage complex release cycles by creating tags and release notes automatically, or maintain repository security by listing and auditing webhooks and CI/CD secrets. It also excels in cross-repository management, allowing the agent to audit milestones, labels, and pull requests across multiple projects simultaneously.

Example Prompts

1. "Check for any open pull requests in the project openclaw/core that require my review and list them in a table format."
2. "Create a new issue in the current repository titled 'Refactor login logic' with a description explaining the need for better error handling."
3. "List all active webhooks for my organization and report any that are not using HTTPS."

Tips & Limitations

• Authentication: Always use the --login flag if you have multiple Gitea instances configured to avoid context confusion.
• Output Control: Utilize the --output flag (e.g., json, yaml, csv) when you need to pipe data from this skill into other automated workflows.
• Scope: Note that some commands are repository-specific. If you are not inside a git repository folder, you must explicitly provide the --repo owner/repo argument.
• Permissions: Ensure your Gitea API token has the necessary scopes for the actions you intend to perform (e.g., repository admin for webhooks).