Menu
Add, list, and edit comments on Gitea/Forgejo issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Create Gitea/Forgejo pull requests — interactive, with flags, from forks, WIP conventions, and quick patterns.
Manage Gitea/Forgejo issue dependencies — add, remove, list, find ready issues, and visualize dependency graphs.
Pin, react to, and lock/unlock Gitea/Forgejo issues via bundled actions.
Label naming conventions, color schemes, export/import, copy between repos, bulk operations, and org-level labels.
List and show Gitea/Forgejo pull requests — filters, fields, detail views, and finding PRs needing review.
Merge Gitea/Forgejo pull requests — all merge styles, auto-merge, mark WIP ready, and branch cleanup.
Based on SOC occupation classification
| name | issue-comments |
| description | Add, list, and edit comments on Gitea/Forgejo issues. |
| user-invokable | true |
tea comment 42 "This is a comment"
tea issues 42 --comments
The tea CLI can't edit comments. For the bundled action, see actions/issues/README.md.
When resolving actions/... paths, use the actions/ directory bundled relative to this skill directory.
Pass explicit scope flags (--login, --remote, or --repo) to bundled actions when the user names a login, remote, backend, or repository. Otherwise, bundled actions use active-host-first discovery.
The comment ID can be found in the JSON output of tea issues <num> --comments or via Forgejo/Gitea UI/API details.