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

22
docs/writing-skills.md
View File

@@ -14,7 +14,7 @@ Skills live in the `skills/` directory, each in its own folder:
```
skills/
├── forgejo/
├── gitea/
│ └── SKILL.md
├── issue-writing/
│ └── SKILL.md
@@ -75,7 +75,7 @@ Document pitfalls to avoid.
Quick-reference tables, checklists, or commands.
```
Not every skill needs all sections—include what's relevant. Some skills are primarily patterns (like `issue-writing`), others are reference-heavy (like `forgejo`).
Not every skill needs all sections—include what's relevant. Some skills are primarily patterns (like `issue-writing`), others are reference-heavy (like `gitea`).
## How Skills are Loaded
@@ -103,7 +103,7 @@ Agents list their skills explicitly:
# Product Manager Agent
## Skills
- forgejo
- gitea
- issue-writing
- backlog-grooming
- roadmap-planning
@@ -121,7 +121,7 @@ Skills can mention other skills for related knowledge:
...
When creating issues, follow the patterns in the **issue-writing** skill.
Use **forgejo** commands to create the issues.
Use **gitea** commands to create the issues.
```
This creates a natural knowledge hierarchy without duplicating content.
@@ -136,7 +136,7 @@ This creates a natural knowledge hierarchy without duplicating content.
- Avoid generic names: `utils`, `helpers`, `common`
Good names:
- `forgejo` - Tool-specific knowledge
- `gitea` - Tool-specific knowledge
- `issue-writing` - Activity-focused
- `backlog-grooming` - Process-focused
- `roadmap-planning` - Task-focused
@@ -147,7 +147,7 @@ The H1 title in `SKILL.md` should match the folder name in Title Case:
| Folder | Title |
|--------|-------|
| `forgejo` | Forgejo CLI (fj) |
| `gitea` | Forgejo CLI (fj) |
| `issue-writing` | Issue Writing |
| `backlog-grooming` | Backlog Grooming |
| `roadmap-planning` | Roadmap Planning |
@@ -266,9 +266,9 @@ Skills should reflect current practices. When workflows change:
Let's examine the existing skills to understand effective patterns.
### Example 1: forgejo (Tool Reference)
### Example 1: gitea (Tool Reference)
The `forgejo` skill is a **tool reference**—it documents how to use a specific CLI tool.
The `gitea` skill is a **tool reference**—it documents how to use a specific CLI tool.
```markdown
# Forgejo CLI (fj)
@@ -276,15 +276,15 @@ The `forgejo` skill is a **tool reference**—it documents how to use a specific
Command-line interface for interacting with Forgejo repositories.
## Authentication
The `fj` CLI authenticates via `fj auth login`. Credentials are stored locally.
The `tea` CLI authenticates via `tea auth login`. Credentials are stored locally.
## Common Commands
### Issues
\```bash
# List issues
fj issue search -s open # Open issues
fj issue search -s closed # Closed issues
tea issue search -s open # Open issues
tea issue search -s closed # Closed issues
...
\```
```