update skills dir

skills/tea/SKILL.md

@@ -20,6 +20,16 @@ Use this skill when you need to:
 
 The `tea` CLI tool interacts directly with Gitea instances via their API. It automatically detects repository context from your current directory and uses stored login credentials.
 
+## ⚠️ Critical Requirements
+
+**BEFORE running any `tea` commands, you MUST:**
+
+1. **Be inside a git repository directory** - Navigate to a repository with `cd /path/to/repo`
+2. **Have a Gitea remote configured** - The repository must have a remote pointing to your Gitea instance (e.g., git.ajet.fyi)
+3. **Be authenticated** - Run `tea whoami` to verify you're logged in
+
+Most `tea` commands will FAIL if you're not in a repository directory with a Gitea remote. The `--repo` flag exists but is unreliable for many operations.
+
 ## Setup
 
 ### Check if logged in
@@ -218,13 +228,21 @@ tea open 42  # Open issue/PR #42
 
 ### Repository Context
 
-Tea automatically detects the repository from your current directory. Override with:
+**REQUIREMENT**: Tea requires you to be in a git repository directory with a Gitea remote configured. It reads `.git/config` to determine the repository context.
 
+**Verify your repository has a Gitea remote:**
 ```bash
-tea pr ls --repo owner/repo
-tea issues create --repo owner/repo -t "Title"
+git remote -v
+# Should show a remote pointing to your Gitea instance (e.g., git.ajet.fyi)
 ```
 
+**If no Gitea remote exists, add one:**
+```bash
+git remote add origin https://git.ajet.fyi/owner/repo.git
+```
+
+**The `--repo` flag is unreliable** - While tea provides a `--repo owner/repo` flag, many commands don't work correctly with it. Always run tea from within the repository directory.
+
 ### Login Selection
 
 Use a specific Gitea login:
@@ -282,37 +300,60 @@ tea pr ls --limit 50
 
 ## Important Notes
 
-- **Repository context**: Tea works best when run from within a git repository directory
-- **Multiple logins**: You can configure multiple Gitea instances
+- **Repository context REQUIRED**: You MUST run tea from within a git repository directory that has a Gitea remote configured. Commands will fail otherwise.
+- **Verify before running**: Always check `git remote -v` to ensure you have a Gitea remote before running tea commands
+- **Navigate to repo first**: Use `cd /path/to/repo` to change to your repository directory before running tea
+- **Multiple logins**: You can configure multiple Gitea instances with `tea login add`
 - **Default login**: Set a default login with `tea login default`
-- **Token permissions**: Ensure your access token has appropriate scopes
+- **Token permissions**: Ensure your access token has appropriate scopes for the operations you need
 - **Help available**: Run `tea <command> --help` for detailed options
 - **Manual pages**: Use `tea man` for comprehensive documentation
 
 ## Typical Workflows
 
+### Pre-flight Checklist
+
+**BEFORE running any tea workflow, verify:**
+
+```bash
+# 1. Check you're in a git repository
+pwd  # Should show your repo directory
+ls .git  # Should exist
+
+# 2. Verify Gitea remote is configured
+git remote -v  # Should show git.ajet.fyi or your Gitea instance
+
+# 3. Check authentication
+tea whoami  # Should show your username
+```
+
+If any of these fail, fix them before proceeding with tea commands.
+
 ### Creating a PR from a feature branch
 
-1. Make changes and commit
-2. Push to remote
-3. Create PR:
+1. **Verify you're in the correct repository directory**
+2. Make changes and commit
+3. Push to remote
+4. Create PR:
    ```bash
    tea pr create -t "Feature: New capability" -d "Description of changes"
    ```
-4. Wait for review or review yourself
+5. Wait for review or review yourself
 
 ### Reviewing and merging a PR
 
-1. List PRs: `tea pr ls`
-2. Checkout locally: `tea pr checkout 42`
-3. Test the changes
-4. Approve: `tea pr approve 42`
-5. Merge: `tea pr merge 42 --style squash`
+1. **Navigate to repository directory**: `cd /path/to/repo`
+2. List PRs: `tea pr ls`
+3. Checkout locally: `tea pr checkout 42`
+4. Test the changes
+5. Approve: `tea pr approve 42`
+6. Merge: `tea pr merge 42 --style squash`
 
 ### Creating a release
 
-1. Ensure you're on the right branch/commit
-2. Create release:
+1. **Navigate to repository directory**: `cd /path/to/repo`
+2. Ensure you're on the right branch/commit
+3. Create release:
    ```bash
    tea releases create --tag v1.0.0 --title "Version 1.0.0" \
      --note "Release notes" --asset ./binary
@@ -320,10 +361,11 @@ tea pr ls --limit 50
 
 ### Managing issues
 
-1. List open issues: `tea issues ls --state open`
-2. View specific issue: `tea issues 42`
-3. Add comment: `tea comment 42 "Working on this"`
-4. Close when done: `tea issues close 42`
+1. **Navigate to repository directory**: `cd /path/to/repo`
+2. List open issues: `tea issues ls --state open`
+3. View specific issue: `tea issues 42`
+4. Add comment: `tea comment 42 "Working on this"`
+5. Close when done: `tea issues close 42`
 
 ## Getting Help