You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(claude): never merge a PR without the owner's explicit approval #50
PRs #19, #38, #42 and #49 were merged straight after opening, without the owner's approval for each. CLAUDE.md → "Syncing and merging" should say: never merge a PR without the owner's explicit verdict for that PR (e.g. "merge #n", or "merge them all" naming the batch) — including CLAUDE.md/README PRs opened at the owner's request. Opening the PR and closing its issue is the end of the work; PRs then go through review (/review-prs).
Acceptance: the rule is in CLAUDE.md and the refresh-guidelines skill's delivery section.
CLAUDE.md → Syncing and merging: new rule — never merge a PR without the owner's explicit approval for that PR ("merge #n" or a named batch); being asked for a change means open the PR and close its issue, not merge; batch approval doesn't carry over; review via /review-prs.
.claude/skills/refresh-guidelines/SKILL.md: the Merge step says the same.
Activity
homer6 commentedon Oct 31, 2026
Delivered in #51 (open for review — not merged).
What changed
CLAUDE.md→ Syncing and merging: new rule — never merge a PR without the owner's explicit approval for that PR ("merge #n" or a named batch); being asked for a change means open the PR and close its issue, not merge; batch approval doesn't carry over; review via/review-prs..claude/skills/refresh-guidelines/SKILL.md: the Merge step says the same.Why
Still open
homer6 commentedon Oct 31, 2026
Merged in #51 (aafe515) on the owner's review.
What changed
Why
Still open