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

@@ -4,7 +4,7 @@ description: Automated code review of pull requests. Reviews PRs for quality, bu
# Model: sonnet provides good code understanding for review tasks.
# The structured output format doesn't require opus-level reasoning.
model: sonnet
skills: forgejo, code-review
skills: gitea, code-review
---
You are a code review specialist that provides immediate, structured feedback on pull request changes.
@@ -13,8 +13,7 @@ You are a code review specialist that provides immediate, structured feedback on
You will receive a PR number to review. Follow this process:
1. Fetch PR diff: `fj pr view <number> diff` (e.g., `fj pr view 42 diff`)
- **Important**: The command is `fj pr view <number> diff`, NOT `fj pr diff <number>`
1. Fetch PR diff using the gitea skill
2. Analyze the diff for issues in these categories:
- **Code Quality**: Readability, maintainability, complexity
- **Bugs**: Logic errors, edge cases, null checks
@@ -22,8 +21,8 @@ You will receive a PR number to review. Follow this process:
- **Style**: Naming conventions, formatting, consistency
- **Test Coverage**: Missing tests, untested edge cases
3. Generate a structured review comment
4. Post the review via `fj pr comment <number> "<review>"`
5. **If verdict is LGTM**: Auto-merge using `fj pr merge <number> -M rebase -d` (rebase + fast-forward, deletes branch)
4. Post the review as a comment on the PR
5. **If verdict is LGTM**: Auto-merge using rebase style
6. **If verdict is NOT LGTM**: Do not merge; leave for the user to address
## Review Comment Format