Hugo Nijhuis
5ad27ae040
Users were confused by ./scripts/ references, thinking they needed to copy scripts into their project. Scripts are in ~/.claude/skills/worktrees/scripts/ and should be referenced with full paths. Changes: - Updated spawn-issues to use full script paths - Updated worktrees skill with full paths in all examples - Fixed gitea model name to claude-haiku-4-5 - Added tools list to issue-worker agent Co-Authored-By: Claude Code <noreply@anthropic.com>
154 lines
4.9 KiB
Markdown
154 lines
4.9 KiB
Markdown
---
|
|
name: gitea
|
|
model: claude-haiku-4-5
|
|
description: View, create, and manage Gitea issues and pull requests using tea CLI. Use when working with issues, PRs, viewing issue details, creating pull requests, adding comments, merging PRs, or when the user mentions tea, gitea, issue numbers, or PR numbers.
|
|
user-invocable: false
|
|
---
|
|
|
|
# Gitea CLI (tea)
|
|
|
|
Command-line interface for Gitea repositories. Use `tea` for issue/PR management in Gitea instances.
|
|
|
|
**Setup required?** See [reference/setup.md](reference/setup.md) for installation and authentication.
|
|
|
|
## Repository Detection
|
|
|
|
`tea` automatically detects the repository from git remotes when run inside a git repository. Use `--remote <name>` to specify which remote to use.
|
|
|
|
## Issues
|
|
|
|
```bash
|
|
# List issues
|
|
tea issues # Open issues (default)
|
|
tea issues --state all # All issues
|
|
tea issues --state closed # Closed issues
|
|
|
|
# View issue details
|
|
tea issues <number> # Full issue details
|
|
tea issues <number> --comments # Include comments
|
|
|
|
# Create issue
|
|
tea issues create --title "<title>" --description "<body>"
|
|
tea issues create -t "<title>" -d "<body>"
|
|
|
|
# Edit issue
|
|
tea issues edit <number> --title "<new-title>"
|
|
tea issues edit <number> --description "<new-body>"
|
|
|
|
# Close/reopen
|
|
tea issues close <number>
|
|
tea issues reopen <number>
|
|
|
|
# Labels
|
|
tea issues edit <number> --labels "bug,help wanted"
|
|
|
|
# Dependencies
|
|
tea issues deps list <number> # List blockers for an issue
|
|
tea issues deps add <issue> <blocker> # Add dependency (issue is blocked by blocker)
|
|
tea issues deps add 5 3 # Issue #5 depends on #3
|
|
tea issues deps add 5 owner/repo#3 # Cross-repo dependency
|
|
tea issues deps remove <issue> <blocker> # Remove a dependency
|
|
```
|
|
|
|
## Pull Requests
|
|
|
|
```bash
|
|
# List PRs
|
|
tea pulls # Open PRs (default)
|
|
tea pulls --state all # All PRs
|
|
tea pulls --state closed # Closed/merged PRs
|
|
|
|
# View PR
|
|
tea pulls <number> # PR details
|
|
tea pulls <number> --comments # Include comments
|
|
|
|
# View PR diff (tea doesn't have a diff command, use git)
|
|
tea pulls checkout <number> # First checkout the PR branch
|
|
git diff main...HEAD # Diff against main branch
|
|
|
|
# Create PR
|
|
tea pulls create --title "<title>" --description "<body>"
|
|
tea pulls create -t "<title>" -d "<body>"
|
|
tea pulls create -t "<title>" -d "Closes #<issue>"
|
|
tea pulls create --head <branch> --base main -t "<title>"
|
|
|
|
# Checkout PR locally
|
|
tea pulls checkout <number>
|
|
|
|
# Review/Approve
|
|
tea pulls approve <number> # Approve PR (LGTM)
|
|
tea pulls reject <number> # Request changes
|
|
tea pulls review <number> # Interactive review
|
|
|
|
# Merge
|
|
tea pulls merge <number> # Default merge
|
|
tea pulls merge <number> --style squash # Squash commits
|
|
tea pulls merge <number> --style rebase # Rebase commits
|
|
tea pulls merge <number> --style rebase-merge # Rebase then merge
|
|
|
|
# Clean up after merge
|
|
tea pulls clean <number> # Delete local & remote branch
|
|
```
|
|
|
|
## Comments
|
|
|
|
```bash
|
|
# Add comment to issue or PR
|
|
tea comment <number> "<comment body>"
|
|
tea comment 3 "LGTM, ready to merge"
|
|
|
|
# Multiline comments (use quoted strings with literal newlines)
|
|
tea comment 3 "## Review Summary
|
|
|
|
- Code looks good
|
|
- Tests pass"
|
|
```
|
|
|
|
> **Warning**: Do not use heredoc syntax `$(cat <<'EOF'...EOF)` with `tea comment` - it causes the command to be backgrounded and fail silently.
|
|
|
|
## Repository
|
|
|
|
```bash
|
|
tea repos # List repos
|
|
tea repos <owner>/<repo> # Repository info
|
|
tea clone <owner>/<repo> # Clone repository
|
|
```
|
|
|
|
## Notifications
|
|
|
|
```bash
|
|
tea notifications # List notifications
|
|
tea notifications --mine # Only participating
|
|
```
|
|
|
|
## Output Formatting
|
|
|
|
Most commands support `--output` or `-o` flag:
|
|
- `-o simple` - Plain text
|
|
- `-o table` - Tabular format (default)
|
|
- `-o json` - Machine-readable JSON
|
|
- `-o yaml` - YAML format
|
|
- `-o csv` - CSV format
|
|
|
|
## Specifying Remote/Login
|
|
|
|
```bash
|
|
tea issues --remote gitea # Use specific git remote
|
|
tea issues --login myserver # Use specific login
|
|
tea issues -r owner/repo # Specify repo directly
|
|
```
|
|
|
|
## Tips
|
|
|
|
- **View single issue**: Use `tea issues <number>` (NOT `tea issues view <number>` - there is no `view` subcommand)
|
|
- **PR description flag**: Use `--description` or `-d` (NOT `--body` like gh CLI)
|
|
- Always verify you're in the correct repository before running commands
|
|
- Use `tea issues` to find issue numbers before viewing/editing
|
|
- Reference issues in PR bodies with `Closes #N` for auto-linking
|
|
- Use `--remote gitea` when you have multiple remotes (e.g., origin + gitea)
|
|
- The `tea pulls checkout` command is handy for reviewing PRs locally
|
|
|
|
## Advanced Topics
|
|
|
|
- **CI/Actions debugging**: See [reference/actions-ci.md](reference/actions-ci.md)
|