القائمة
List and show Gitea/Forgejo issues — filters, fields, pagination, detail views, comments, export, and counts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create Gitea/Forgejo pull requests — interactive, with flags, from forks, WIP conventions, and quick patterns.
Add, list, and edit comments on Gitea/Forgejo issues.
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.
| name | list-issues |
| description | List and show Gitea/Forgejo issues — filters, fields, pagination, detail views, comments, export, and counts. |
| user-invokable | true |
# Repository-scoped listing: prefer an explicit remote or repo/login.
tea issues list --remote <git-remote> -o simple # e.g. --remote self-hosted
tea issues list --repo <owner>/<repo> --login <login> -o simple
# Add filters to the same repository-scoped command.
tea issues list --remote <git-remote> --state all -o simple # include closed
tea issues list --remote <git-remote> --labels "bug,critical" -o simple # by label
tea issues list --remote <git-remote> --milestones "v1.0" -o simple # by milestone
tea issues list --remote <git-remote> --assignee "user" --author "user" # by person
tea issues list --remote <git-remote> --keyword "search term" # text search
tea issues list --remote <git-remote> --from "2025-01-01" --until "2025-06-01"
tea issues list --remote <git-remote> --output json # use json only when parsing with jq
tea issues list --remote <git-remote> --fields "index,title,state,labels,assignees"
tea issues list --remote <git-remote> --page 2 --limit 50
tea issues --remote <git-remote> 42 # detail view
tea issues --remote <git-remote> 42 --comments # with comments
# Export all issues in this repository to JSON
tea issues list --remote <git-remote> --state all --output json > issues-backup.json
# Count by state in this repository
echo "Open: $(tea issues list --remote <git-remote> --state open --output json | jq length)"
echo "Closed: $(tea issues list --remote <git-remote> --state closed --output json | jq length)"
Do not use bare tea issues list when the user asks for issues for the current repository; in multi-repo logins it can return issues across repositories.
Prefer -o simple for listing; use --output json only when parsing with jq
--kind pulls searches PRs with the same filters as issues