codebergInteract with Codeberg using the `tea` CLI. Use `tea issue`, `tea pr`, `tea actions`, and `tea api` for issues, PRs, Actions, and advanced queries.
Install via ClawdBot CLI:
clawdbot install razzeee/codebergUse the tea CLI to interact with Codeberg. Codeberg is a Forgejo instance, and the tea CLI is fully compatible with it.
List open pull requests:
tea pulls --repo owner/repoCheck details of a PR:
tea pr 55 --repo owner/repoList open issues:
tea issues --repo owner/repoView an issue:
tea issue 123 --repo owner/repoList repository secrets:
tea actions secrets list --repo owner/repoList repository variables:
tea actions variables list --repo owner/repoThe tea api command is useful for accessing data not available through other subcommands.
Get PR with specific fields (requires jq for filtering):
tea api repos/owner/repo/pulls/55 | jq '.title, .state, .user.login'To use tea with Codeberg, you first need to add your login:
tea login add --name codeberg --url https://codeberg.org --token <your-token>Then you can use --login codeberg in your commands:
tea pulls --repo owner/repo --login codebergList all configured logins:
tea loginsGenerated Feb 23, 2026
Maintainers of open source projects on Codeberg can use this skill to efficiently manage pull requests and issues. It enables quick listing of open PRs and issues, checking their details, and automating workflows with Actions for CI/CD, streamlining collaboration and code review processes.
DevOps teams can leverage the skill to automate repository management tasks, such as monitoring Actions secrets and variables for security compliance. By integrating with the tea CLI, they can script advanced queries via the API to fetch specific PR or issue data, enhancing deployment pipelines and operational oversight.
Researchers using Codeberg for version control can utilize this skill to track issues and PRs related to academic papers or code repositories. It facilitates easy access to repository data, helping teams coordinate contributions and manage project timelines effectively in a collaborative environment.
Freelance developers working on Codeberg-hosted projects can use the skill to quickly check PR statuses and issue details across multiple repositories. This aids in managing client work by providing a unified interface for repository interactions, improving productivity and client communication.
Companies can integrate this skill into their SaaS platforms to offer enhanced Codeberg management features to customers. By leveraging the tea CLI, they can provide automated issue tracking, PR management, and Actions monitoring as part of a subscription service, generating revenue through tiered pricing plans.
Consulting firms can offer services to help organizations set up and optimize their Codeberg workflows using this skill. This includes configuring logins, automating API queries, and integrating with existing tools, with revenue generated from project-based fees or ongoing support contracts.
Educational providers can create training programs and certifications focused on using the tea CLI with Codeberg. By teaching users how to manage PRs, issues, and Actions, they can charge for courses, workshops, and certification exams, building a revenue stream from skill development.
💬 Integration Tip
Ensure the tea CLI is installed and configured with a login token for Codeberg before use; consider automating common commands in scripts for efficiency.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.