sysadminandClaude Opus 4.8
2111c84e7d
Require lease verification (open PRs, branches, worktrees, leases, merged completion) before any issue or PR work. Surface the rule in the portable skill, Gitea runbooks, operator guide, and start-issue template; add doc-contract tests. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
1.6 KiB
1.6 KiB
Workflow Model
Navigation
- Home | Operator Guide | Repositories Map | Identity and Profiles | Workflow Model | Safety and Gates | MCP Tools Reference | Operator Runbooks | Open Decisions | Project History
Step 1: Review queue first (reviewer profile)
gitea_resolve_task_capability(task="review_pr")- List open PRs; pick the oldest eligible PR (not self-authored, mergeable).
- Pin head SHA; validate diff scope and run tests locally.
gitea_mark_final_review_decision→gitea_review_pr/gitea_submit_pr_reviewgitea_merge_pronly withconfirmation="MERGE PR <n>"and pinned head SHA.
Step 2: Implement issues (author profile)
- Work Selection Rule — verify a work lease before any mutations (open PRs, issue-linked PRs, branches, worktrees, dirty worktrees, active leases/ handoffs, merged-PR completion). Stop if another session owns the lease.
gitea_resolve_task_capabilityfor the author task.gitea_lock_issuebefore implementation mutations.- Claim with
gitea_mark_issue/status:in-progresslabel. - Branch, implement, test, push,
gitea_create_pr. - Release claim when done; never self-review the PR.
Step 3: Operator follow-ups
Wiki publication, credential provisioning, and cross-repo mirror operations are operator-confirmed actions — see Runbooks.
Full Gitea-specific runbooks: docs/llm-workflow-runbooks.md in the repository.