From 00f51d02ecfc016bed0af3130b5d74f26c0cd074 Mon Sep 17 00:00:00 2001 From: Astrid Gealer Date: Fri, 16 Oct 2026 12:17:17 +0100 Subject: [PATCH] docs(claude): PR-search limit and shared-login release in the claim rules Bring the issue-assignment section in line with the final wording in cloud-commitments-cli#2202 and cloud-commitments-go#421: cap the open-PR search at --limit 1000 (split if it returns 1000), and keep a shared-login assignment when another worker on that login still holds an active claim. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 77f6866..83605bd 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -100,7 +100,8 @@ coordinates agents on one machine; assignment is what coordinates people. come after `p3`. The query only sees assignees, so open the issue and check its comments for a claim (step 2) too. Before claiming, also check that no open PR already addresses it: - `gh pr list --repo LeanerCloud/cloud-commitments-mcp --search " in:body"`. + `gh pr list --repo LeanerCloud/cloud-commitments-mcp --limit 1000 --search " in:body"` + (split it the same way if it returns 1000). 2. **Claim it before writing any code.** Post a claim comment, and also assign yourself if you have write access. Claims, takeovers and releases @@ -141,6 +142,10 @@ coordinates agents on one machine; assignment is what coordinates people. gh issue edit --repo LeanerCloud/cloud-commitments-mcp --remove-assignee @me ``` + Skip the `--remove-assignee` when another worker on your shared login + still holds an active claim: the assignment is that worker's too, and + removing it would make the issue look unowned. + An assignment with no marker comment (for example a maintainer assigning someone) still means the issue is taken, and so does an older free-form claim comment such as `claimed by `. @@ -169,7 +174,8 @@ coordinates agents on one machine; assignment is what coordinates people. 5. **Release what you drop.** If you stop working on an issue without a PR, post `Released: []` as a new comment - and unassign yourself + and unassign yourself (unless another worker on your shared login + still holds an active claim) (`gh issue edit --repo LeanerCloud/cloud-commitments-mcp --remove-assignee @me`), so the next person can pick it up. If the issue turns out to be already fixed, say which PR or commit fixed it and ask a maintainer to close it.