flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Migrate from Forgejo to Gitea

Browse Source 
- 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:
Hugo Nijhuis
2025-12-30 13:50:00 +01:00
parent c7025a4c98
commit 68675a7e12
20 changed files with 322 additions and 243 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
commands/create-issue.md
View File

@@ -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

9
commands/dashboard.md
View File

@@ -4,9 +4,10 @@ description: Show dashboard of open issues, PRs awaiting review, and CI status.
# Repository Dashboard
Run these commands and present a summary:
Use the gitea skill.
1. **Open Issues**: `fj issue search -s open`
2. **Open PRs**: `fj pr search -s open`
Fetch and display:
1. All open issues
2. All open PRs
Format as tables showing issue/PR number, title, and author.
Format as tables showing number, title, and author.

8
commands/groom.md
View File

@@ -5,11 +5,11 @@ argument-hint: [issue-number]
# Groom Issues
Use the backlog-grooming and issue-writing skills.
Use the gitea, backlog-grooming, and issue-writing skills.
## If issue number provided ($1):
1. **Fetch the issue**: `fj issue view $1`
1. **Fetch the issue** details
2. **Evaluate** against grooming checklist
3. **Suggest improvements** for:
- Title clarity
@@ -17,11 +17,11 @@ Use the backlog-grooming and issue-writing skills.
- Acceptance criteria quality
- Scope definition
4. **Ask user** if they want to apply changes
5. **Update issue** if approved: `fj issue edit $1 --body "..."`
5. **Update issue** if approved
## If no argument (groom all):
1. **List open issues**: `fj issue search -s open`
1. **List open issues**
2. **Review each** against grooming checklist
3. **Categorize**:
- Ready: Well-defined, can start work

4
commands/plan-issues.md
View File

@@ -5,7 +5,7 @@ argument-hint: <feature-description>
# Plan Feature: $1
Use the roadmap-planning, issue-writing, and forgejo skills.
Use the gitea, roadmap-planning, and issue-writing skills.
1. **Understand the feature**: Analyze what "$1" involves
2. **Explore the codebase** if needed to understand context
@@ -29,6 +29,6 @@ Use the roadmap-planning, issue-writing, and forgejo skills.
```
5. **Ask for approval** before creating issues
6. **Create issues** in order using `fj issue create`
6. **Create issues** in order
7. **Update dependencies** with actual issue numbers after creation
8. **Present summary** with links to created issues

14
commands/review-pr.md
View File

@@ -1,12 +1,14 @@
---
description: Review a Forgejo pull request. Fetches PR details, diff, and comments.
description: Review a Gitea pull request. Fetches PR details, diff, and comments.
argument-hint: <pr-number>
---
# Review PR #$1
1. **View PR details**: `fj pr view $1`
2. **Get the diff**: `fj pr view $1 diff`
Use the gitea skill.
1. **View PR details** including description and metadata
2. **Get the diff** to review the changes
Review the changes and provide feedback on:
- Code quality
@@ -15,6 +17,6 @@ Review the changes and provide feedback on:
- Documentation
Ask the user what action to take:
- **Merge**: Post review summary as comment, then `fj pr merge $1 -M rebase -d` (rebase + fast-forward, deletes branch)
- **Request changes**: `fj pr comment $1 "<feedback>"` - Leave feedback without merging
- **Comment only**: `fj pr comment $1 "<comment>"` - Add a comment for discussion
- **Merge**: Post review summary as comment, then merge with rebase style
- **Request changes**: Leave feedback without merging
- **Comment only**: Add a comment for discussion

4
commands/roadmap.md
View File

@@ -4,9 +4,9 @@ description: View current issues as a roadmap. Shows open issues organized by st
# Roadmap View
Use the forgejo skill.
Use the gitea skill.
1. **Fetch all open issues**: `fj issue search -s open`
1. **Fetch all open issues**
2. **Analyze dependencies** from issue descriptions
3. **Categorize issues**:
- Blocked: Waiting on other issues

10
commands/work-issue.md
View File

@@ -1,15 +1,17 @@
---
description: Work on a Forgejo issue. Fetches issue details and sets up branch for implementation.
description: Work on a Gitea issue. Fetches issue details and sets up branch for implementation.
argument-hint: <issue-number>
---
# Work on Issue #$1
1. **View the issue**: `fj issue view $1`
Use the gitea skill.
1. **View the issue** to understand requirements
2. **Create a branch**: `git checkout -b issue-$1-<short-kebab-title>`
3. **Plan**: Use TodoWrite to break down the work based on acceptance criteria
4. **Implement** the changes
5. **Commit** with message referencing the issue
6. **Push**: `git push -u origin <branch>`
7. **Create PR**: `fj pr create "[Issue #$1] <title>" --body "Closes #$1"`
6. **Push** the branch to origin
7. **Create PR** with title "[Issue #$1] <title>" and body "Closes #$1"
8. **Auto-review**: Inform the user that auto-review is starting, then spawn the `code-reviewer` agent in background (using `run_in_background: true`) with the PR number