sysadminandClaude Opus 4.8
f58317d079
Bootstrap repo-tracked wiki pages (10 required pages), the operator- confirmed sync script, PR template publication gate, and safety tests so Gitea-Tools can publish to the live Gitea Wiki per issue #224. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
1.8 KiB
1.8 KiB
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
- Verify identity first — Run
gitea_whoamiand confirm the active profile before any mutation. - Resolve task capability — Call
gitea_resolve_task_capabilityfor the intended task before gated tools. - 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.
- No self-review / no self-merge — The authenticated Gitea user must not approve or merge a PR they authored.
- 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
gitea_whoami— confirm authenticated user and profile.gitea_get_runtime_context— allowed/forbidden operations for this session.gitea_resolve_task_capability— prove the session may perform the planned task.- For reviewer work: dry-run validation (
gitea_dry_run_pr_review) before live review mutations.