docs: propose verifier-bound skill scorecards - #570
Conversation
Co-Authored-By: Cursor <cursoragent@cursor.com>
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: escoffier-labs/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Blocking readiness on one stale dependency reference:
I found no other issue in the scorecard decomposition or its four filed implementation slices. |
Summary
Current failure mode
scored_artifact_countis only the number of distinct artifact ids with parsed outcome rows. Capture is opt-in, rank is read-only, and only explicitbrigade outcome reconcile --applyadvances promotion state. The proposal does not treat the reported 1,601 existing rows as trustworthy training data.Verification
brigade work verify run --target . --command "git diff --cached --check" --command "brigade handoff lint --target . .claude/memory-handoffs/2026-07-26-skill-scorecards-planning.md" --capture brigade-work20260726-223449-work-verify-3713cb68adffeab4dd404c3b95b47dRefs #502 and #503.