Skip to content

CLAUDE.md: documentation, PR, stacking and review rules - #409

Open
bkontur wants to merge 11 commits into
devfrom
bko-claude-md-pr-descriptions
Open

CLAUDE.md: documentation, PR, stacking and review rules#409
bkontur wants to merge 11 commits into
devfrom
bko-claude-md-pr-descriptions

Conversation

@bkontur

@bkontur bkontur commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Agent rules in CLAUDE.md, prompted by the #403#408 stack: unrelated PRs stacked on each other, descriptions that restated the diffs, and a hand-written weights paragraph shipped for review.

New rules

  • Docs are short and do not restate code.
  • PR descriptions: one or two sentences on what and why, then bulleted Changes / Cleanup / Follow-ups / Open questions sections as needed.
  • Stacking only for real dependencies; base PR and merge order in the description.
  • Regenerated files (bindings, metadata, weights) in their own commit.
  • Extrinsics benchmarked with /cmd bench before review.
  • Reviews of stacked PRs cover the stack shape; the author does any history rewrite.

Cleanup

  • Merged the three "flag, don't fix" bullets into one, and the two code-review bullets into one.
  • Replaced the "Claude review bot" section, which had no workflow behind it, with the real /aireview trigger.
  • Moved "public APIs need rustdoc" into the documentation rules.
  • Removed dead .claude/ entries: the test skill (no SKILL.md, wrong crate names and paths), the review-pr command (subset of /review), and the README that described only those two.

Follow-ups

What the PR does and why, follow-ups, open questions. No fluff.
Stack only on a real dependency, each PR still self-contained; never stack
unrelated work. Name the base PR in the description; merge bottom-up.
Generated-file conflicts (bindings, metadata, weights) are not a reason
to stack, and a stacked PR must say what it stacks on and in which order
the stack merges. Descriptions are kept current as the PR changes.
Diff each PR against its own base, check every link is a real
dependency, and propose a restructure instead of only flagging it.
Every added or edited doc is simple and to the point: no fluff, no
restating the code or the diff, no boilerplate.
@bkontur bkontur changed the title CLAUDE.md: PR description and stacked-PR rules CLAUDE.md: documentation, PR description and stacked-PR rules Sep 10, 2026
@bkontur
bkontur requested a review from mudigal September 10, 2026 13:49
@bkontur bkontur changed the title CLAUDE.md: documentation, PR description and stacked-PR rules CLAUDE.md: documentation, PR, stacking and review rules Sep 10, 2026
…e overlapping rules

The stacked-PR review rule said "rebase onto dev" while the git rules
forbid rebase and force-push; it now says retarget, and the author does
any history rewrite. The Claude review bot section described a bot with
no workflow behind it; the actual trigger is /aireview. Three overlapping
design bullets and two overlapping review bullets are merged. New rules:
regenerated files in their own commit, benchmark new extrinsics before
review, public APIs need rustdoc moved under documentation.
…e README

- skills/test/pallet.md has no SKILL.md so it is never loaded, and its
  content is wrong: crate names that do not exist (storage-provider-pallet),
  a /runtime path (runtimes/ now), and tarpaulin where CI uses
  scripts/coverage.sh.
- commands/review-pr.md is a subset of the /review skill, which CLAUDE.md
  names as the authoritative review criteria.
- README.md documented only those two entries and none of the five real
  skills.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant