docs(skill): teach the Claude Code plugin to derive BECs from a CLAUDE.md (F4)

[DataDave-Dev]

Why (F4 — closes the agent/MCP layer)

F1–F3 built the MCP tools (preview_rule, propose_rules_from_claude_md,
add_rule). F4 teaches the Claude Code skill/plugin to actually use them, so an
agent session turns the deterministic parts of a CLAUDE.md into BECs — and,
crucially, knows what not to convert.

What

Updates integrations/claude-code/ (skill, command, plugin README):

• New "Deriving BECs from a CLAUDE.md" section in the skill. The rule of
  thumb: deterministic → BEC; judgment-based → stays in CLAUDE.md ("if you can't
  name a check that verifies it, it's not a BEC"). Fast path: --from-claude-md.
  Thorough path: the MCP loop — propose_rules_from_claude_md (start) →
  list_checks (vocabulary) → preview_rule (validate before writing) →
  add_rule(confirm=true) (persist, after showing the user).
• Baseline pattern documented as the default for adopting on a dirty repo.
• Checks list refreshed: adds require, max_lines, filename, and exclude:.
• MCP mention updated to list all five tools.
• /becwright init now picks the right flavor (--from-claude-md / --baseline)
  and offers the MCP loop when the server is connected.

Skill/plugin (markdown) only — no code, no rule-format change.

The full line this completes

"Make more of CLAUDE.md deterministic": 3 agnostic checks (#44) → max_lines
auto-mapping (#45) → MCP tools F1–F3 (#46, #47, #48) → the skill that drives
them (F4). becwright guarantees execution; the agent does the translation.

Test plan

• Full suite still green (204 passed) — markdown-only change, dogfooded
• Skill/command/README internally consistent with the shipped tools & checks

[coderabbitai]

Warning

Review limit reached

@DataDave-Dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6f2622e4-b5dd-42c4-9dfc-b13d74ff21b4

📥 Commits

Reviewing files that changed from the base of the PR and between d5cfc86 and 3b3fd17.

📒 Files selected for processing (4)

• CHANGELOG.md
• integrations/claude-code/README.md
• integrations/claude-code/commands/becwright.md
• integrations/claude-code/skills/becwright/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/cc-skill-agent-flow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}