forgejo-maintainer
SkillDev toolsAdminister Forgejo or Gitea installations, including upgrades, backups, migrations, repository access, and Actions runners. Use for application-specific operations, not general Linux host troubleshooting.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the forgejo-maintainer skill
What this skill tells your AI
The instructions your AI receives, as published by christitustech/titus-ai in .agents/skills/forgejo-maintainer/SKILL.md and read by ahel’s review.
Workflow
- Establish the deployment method, Forgejo version, database, storage paths, configuration, and runner topology.
- Separate application failures from host, network, container, and reverse proxy failures; use the narrower skill for substantial work in those layers.
- Determine impact to Git, web, SSH, packages, and Actions, then create rollback with database and data backups.
- Make the smallest application-specific change and validate every affected access path.
Diagnostics
systemctl status forgejo
journalctl -xeu forgejo
forgejo --version
df -h
findmnt
ss -tulpn
ssh -T git@<host>
curl -I <root-url>
Safety Rules
- Never upgrade before taking database and data backups.
- Never trust a backup policy until restore has been tested.
- Never expose runner registration tokens in logs or docs.
- Preserve
app.ini, repositories, LFS objects, attachments, packages, and custom templates. - Isolate Actions runners by trust boundary.
Validation
- Web login and repository browsing work.
- HTTPS clone and SSH clone work.
- Push and pull work for a test repository.
- Actions runners register and run a small job when applicable.
- Backup artifacts exist and restore steps are documented.
Signals
- GitHub stars
- 125
- Forks
- 21
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
forgejo-maintainer- Source
- github.com/christitustech/titus-ai