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:
@@ -1,17 +1,19 @@
|
||||
---
|
||||
description: Create a new Forgejo issue. Can create single issues or batch create from a plan.
|
||||
description: Create a new Gitea issue. Can create single issues or batch create from a plan.
|
||||
argument-hint: [title] or "batch"
|
||||
---
|
||||
|
||||
# Create Issue(s)
|
||||
|
||||
Use the gitea skill.
|
||||
|
||||
## Single Issue (default)
|
||||
If title provided: `fj issue create "$1" --body "<description>"`
|
||||
If title provided, create an issue with that title and ask for description.
|
||||
|
||||
## Batch Mode
|
||||
If $1 is "batch":
|
||||
1. Ask user for the plan/direction
|
||||
2. Generate list of issues with titles and descriptions
|
||||
3. Show for approval
|
||||
4. Create each: `fj issue create "<title>" --body "<body>"`
|
||||
4. Create each issue
|
||||
5. Display all created issue numbers
|
||||
|
||||
Reference in New Issue
Block a user