Migrate from Forgejo to Gitea

- Replace fj CLI with tea CLI across all commands
- Create new gitea skill, remove forgejo skill
- Update all agents to use gitea skill
- Update commands to use skill-based approach (reference skills instead of embedding CLI commands)
- Update all documentation (README, ARCHITECTURE, VISION, writing guides)
- Swap git remotes: origin now points to git.flowmade.one (Gitea)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2025-12-30 13:50:00 +01:00
parent c7025a4c98
commit 68675a7e12
20 changed files with 322 additions and 243 deletions

View File

@@ -25,16 +25,16 @@ ai/
All files symlink to `~/.claude/` via `make install`.
## Forgejo Integration
## Gitea Integration
Uses `fj` CLI (forgejo-cli) for issue/PR management:
Uses `tea` CLI for issue/PR management:
```bash
# Setup (one-time)
brew install forgejo-cli
echo "YOUR_TOKEN" | fj -H code.flowmade.one auth add-key username
brew install tea
tea logins add --name flowmade --url https://git.flowmade.one --token <your-token>
# Token needs scopes: read:user, read:repository, write:issue, write:repository
# Create token at: https://git.flowmade.one/user/settings/applications
```
### Available Commands