forgejo

What This Skill Does

The Forgejo skill empowers your OpenClaw AI agent to interface directly with Forgejo instances using the powerful tea command-line interface. This integration allows the agent to act as a bridge between your conversational requests and your software development lifecycle. Whether you are managing pull requests, triaging issues, checking CI/CD status via Actions, or performing complex data retrieval through the Forgejo API, this skill streamlines these developer operations significantly.

Installation

To integrate this skill into your environment, run the following command within your OpenClaw terminal:

clawhub install openclaw/skills/skills/razzeee/forgejo

Ensure that you have the tea CLI installed on your host system and configured with at least one login profile using tea login add before requesting the agent to perform actions.

Use Cases

This skill is ideal for developers and DevOps engineers looking to automate their Git workflow. Common use cases include:

• Automating issue triage: Ask the agent to list all open issues and summarize the most urgent ones.
• CI/CD Monitoring: Have the agent verify the state of your repository secrets or variables to ensure pipeline health.
• PR Management: Use the agent to retrieve specific pull request details, review comments, or identify missing approvals.
• Advanced Reporting: Query complex repository data using the tea api command to extract specific metadata about your project health or contributor activity.

Example Prompts

1. "List all open pull requests for the repository 'openclaw/openclaw' and tell me how many are currently marked as needing review."
2. "Check the Forgejo secrets configuration for the 'my-project' repository to ensure the deployment tokens are still active."
3. "Fetch the title and user login for pull request #45 in 'my-org/backend-service' and summarize the request."

Tips & Limitations

• Authentication: Always ensure your Forgejo access tokens are securely managed. The agent will use the login profiles you have explicitly defined in the tea CLI configuration.
• Dependency: This skill relies heavily on tea. If a feature is not supported by tea, the agent will fall back to tea api, which may require additional jq knowledge to parse complex JSON responses effectively.
• Context Limits: Large API responses might exceed token windows if you request too much data at once. Filter your API calls specifically where possible.
• Permissions: Ensure the token provided to tea has the necessary read/write permissions for the specific repositories you want the agent to manipulate.