feat(roster): add missing primitive skills (bookkeeping/persist/dogfood) + fix kg P6 mistag (BRO-1586)

[broomva]

BRO-1586 — add the missing primitive implementations to the roster

Follow-up to #81. The roster claimed to be the bstack-stack but omitted core primitive implementations. Careful curation pass — 56 → 61 entries, all broomva/skills, descriptions taken from each skill's real frontmatter:

Skill	category	primitive	required
bookkeeping	knowledge	P6	✅ (universal knowledge engine)
persist	orchestration	P12	✅ (Persistent Loop Discipline)
dogfood	lifecycle	P11	✅ (Empirical feedback / Dogfood)
skillify	meta	—	optional (skill-creation gate)
checkit	knowledge	—	optional (role-x/P17 lens)

Fix: kg's P6 mistag

kg was tagged primitive: P6, but P6 is Bookkeeping — bookkeeping's own frontmatter declares primitive: P6, and kg's own description says it "pairs with bookkeeping's cmd_index." Dropped kg's primitive tag → one canonical P6 = bookkeeping. kg stays required/knowledge.

Scope (deliberate)

Not added: agentic-vps, architecture-design-principles, broomva-cli, design-engineering, colombia-conflict — general capability skills, not bstack-native primitives/core. skills-roster.md not row-mirrored (its banner already makes the YAML authoritative + itself a broader catalog; the doc uses global numbering, so a 5-row insert would force a fragile renumber).

Validated

• schema-valid · no duplicate primitive tags (P6/P11/P12 each → exactly one) · no dup names
• drift-guard remote resolution: all 61 resolve in broomva/skills
• installer uses --skill <name> for all 61 (bstack-skills list shows the new tags correctly)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@broomva, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 37 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d32ad243-71e6-43ec-9da0-3ee27197261e

📥 Commits

Reviewing files that changed from the base of the PR and between bd239b9 and c78698a.

📒 Files selected for processing (1)

• references/companion-skills.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bro-1586-roster-add-primitives

---

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.}