Skip to content

docs(claude): PR-search limit and shared-login release in the claim rules #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cristim merged 1 commit into from
Oct 16, 2026
Merged

docs(claude): PR-search limit and shared-login release in the claim rules #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 "<issue number> in:body"`.
`gh pr list --repo LeanerCloud/cloud-commitments-mcp --limit 1000 --search "<issue number> 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
Expand Down Expand Up @@ -141,6 +142,10 @@ coordinates agents on one machine; assignment is what coordinates people.
gh issue edit <N> --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 <worker>`.
Expand Down Expand Up @@ -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: <where you got to> [<worker-id>]` 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 <N> --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.
Expand Down
Loading