open-weight/skills/issue-tracker/SKILL.md
Use when creating, reading, updating, listing, searching, transitioning, or commenting on issues or tickets. Use when the user references a ticket ID, issue number, or asks to "open an issue", "close a ticket", "add a comment", "list issues", "search for tickets", "transition to in progress", or similar.
npx skillsauth add jon23d/skillz issue-trackerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
All issue operations use the tea CLI. Do not use webfetch, curl, or the web UI.
Check availability first:
tea --version
If tea is not found, stop and tell the user to install it from https://gitea.com/gitea/tea. Assume it is already authenticated. Run all commands from the repo root.
List issues:
tea issues ls # open issues (default)
tea issues ls --state closed
tea issues ls --state all
tea issues ls --assignee <username>
tea issues ls --label <label>
Read a specific issue:
tea issue <NUMBER>
Create an issue:
cat > /tmp/issue-body.md << 'EOF'
...
EOF
tea issues create --title "..." --description "$(cat /tmp/issue-body.md)"
Edit an issue (use --add-assignees to assign, not --assignees):
tea issues edit <number> --title "..."
tea issues edit <number> --description "$(cat /tmp/body.md)"
tea issues edit <number> --add-assignees <username>
tea issues edit <number> --add-labels <label>
Close / reopen:
tea issues close <number>
tea issues reopen <number>
Add a comment (comment is a top-level command, body is a positional arg — no --body flag):
tea comment <number> "Your comment here"
# Multi-line:
cat > /tmp/comment.md << 'EOF'
...
EOF
tea comment <number> "$(cat /tmp/comment.md)"
Write multi-line content to a temp file and use $(cat /tmp/file.md) to avoid shell-escaping issues.
Gitea has no attachment upload via tea — commit files to the branch and link them inline instead.
development
Use when adding or modifying environment variable handling in TypeScript projects or monorepos — especially when using process.env directly, missing startup validation, sharing env schemas across packages, or encountering "undefined is not a string" errors at runtime from missing env vars.
testing
Use when creating a new skill, editing an existing skill, writing a SKILL.md, or verifying a skill works before deployment.
development
React UI design principles and conventions. Load when building or modifying any user interface or React components. Covers application type detection, visual standards, component design and structure, Mantine (business apps) and Tailwind (consumer apps), accessibility, responsiveness, state management, data fetching, testing, and in-app help patterns.
development
Use when setting up ESLint and/or Prettier in a TypeScript project, adding linting to an existing TypeScript codebase, or configuring typescript-eslint, eslint-config-prettier, or related packages.