Gitea Issue Check Skill
Prerequisites
- •Active Role: Must be in a Role Context (e.g.,
//office @rd). - •Configuration:
GEMINI.mdmust defineGitea.Authpath.
Workflow
1. Verify Identity & Configuration
- •Goal: Confirm operational context.
- •Action: Read the active
GEMINI.md. - •Check:
- •
Gitea.User: The Gitea Username (e.g.,rd,rory-agent). - •
Gitea.Auth: Path to credential file (e.g.,private/auth/.rd-env).
- •
2. Authenticate
- •Goal: Ensure
teaCLI has valid credentials. - •Action:
bash
# Activate Mise Environment (Profile) eval "$(MISE_ENV=<Gitea.User> mise activate)" # auto-register if missing (uses env vars from mise profile) if ! tea login list --output simple | grep -q "^<Gitea.User>"; then tea login add --name "<Gitea.User>" --url "https://gitea.gnomatix.com" --token "${GITEA_ISSUES_USER_AUTH_TOKEN}" --insecure fi
3. Fetch Assigned Issues
- •Goal: Retrieve active backlog.
- •Action:
bash
tea issues ls --assignee <Gitea.User> --state open --fields index,title,state,author,labels,updated
4. Triage Loop (Per Issue)
For each relevant issue:
- •Read Context:
tea issue <id>andtea issue comments <id>. - •Analyze:
- •New Request: Acknowledge and add to
task.md. - •Blocked: Comment requesting info.
- •Done: Close issue (
tea issue close <id>).
- •New Request: Acknowledge and add to
- •Execute: Perform necessary work or updates.
5. Synchronize State
- •Goal: Align Local Brain with Remote Truth.
- •Action: Update
task.mdto reflect new priorities or closed items.