Repository navigation
docs: spec-number allocation rule (collision guard) - #33
Conversation
…g repo before claiming (two spec-142s collided 2026-06-12)
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5c6576b1fc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | grep -oE 'spec-[0-9]+' | sort -uV | tail -1`, open PRs touching `docs/spec-*` | ||
| (`gh pr list --search "spec-" --state open`), and sibling repo edge-book-host's |
There was a problem hiding this comment.
When an open PR adds a file such as docs/spec-145-foo.md but its title/body/comments do not contain spec-, this check misses the reservation even though the text says to find PRs touching docs/spec-*. I checked the gh pr list docs: --search uses GitHub issue/PR search syntax, and GitHub's issue search docs say unqualified terms search only the title, body, and comments, not changed file paths. Agents following this collision guard can still pick an in-use spec number; use PR file lists/diffs (for example gh pr diff --name-only per open PR or the PR files API) for this step.
Useful? React with 👍 / 👎.
1 participant
Two sessions claimed spec-142 on the same day (self-update merged in #32; activation-funnel renumbered to spec-144). Adds the allocation convention to CLAUDE.md: next free number across docs/, open PRs, and edge-book-host; loser of a race renumbers the unmerged spec. Docs-only.
🤖 Generated with Claude Code