1

Operator Guide

Jason Walker edited this page 2026-07-06 01:36:36 -04:00

Table of Contents

• Operator Guide
• Navigation
• Key rules
• Supported Gitea instances
• New session checklist

Operator Guide

Navigation

• Home | Operator Guide | Repositories Map | Identity and Profiles | Workflow Model | Safety and Gates | MCP Tools Reference | Operator Runbooks | Open Decisions | Project History

Handbook for LLM operators and human developers using the Gitea-Tools MCP server.

Key rules

1. Verify identity first — Run gitea_whoami and confirm the active profile before any mutation.
2. Resolve task capability — Call gitea_resolve_task_capability for the intended task before gated tools.
3. One unit of work per session — Implement one claimed issue or review/merge one PR; do not mix author and reviewer mutations in one session.
4. No self-review / no self-merge — The authenticated Gitea user must not approve or merge a PR they authored.
5. Follow the gates — Prompts express intent; MCP tools enforce safety. Never bypass gates via prompt instructions.

Supported Gitea instances

Remote	Host	Default org/repo
dadeschools	gitea.dadeschools.net	Contractor / Timesheet
prgs	gitea.prgs.cc	Scaled-Tech-Consulting / Timesheet

Always pass remote explicitly on tool calls. The server default is dadeschools; forgetting remote on a prgs task hits the wrong host.

New session checklist

1. gitea_whoami — confirm authenticated user and profile.
2. gitea_get_runtime_context — allowed/forbidden operations for this session.
3. gitea_resolve_task_capability — prove the session may perform the planned task.
4. For reviewer work: dry-run validation (gitea_dry_run_pr_review) before live review mutations.