rubric-rebackport

Stamp legacy review directories with rubric identifiers and rescoring metadata.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill rubric-rebackport
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rubric-rebackport
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/rubric-rebackport
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill rubric-rebackport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy review directories created before the post-#346 rubric stamping era lack the rubric_id, rubric_total, and advance_threshold fields needed for apples-to-apples comparison across rubric migrations. Manually updating dozens of pre-/44 memo, proposal, and other artifact reviews is error-prone and time-consuming.

Core Features & Use Cases

  • Stamp-only mode: Infers the correct rubric identity from existing metadata or operator assertions and writes the three required stamping fields directly into legacy _meta.json files, plus updates sibling _progress.json score history and _summary.md rubric blocks.
  • Rescore mode: Creates immutable sidecar review directories containing fresh scores computed under the current /44 rubric, leaving the original legacy review byte-identical for audit trails.
  • Idempotent bridge tool: Runs dry-run by default, applies changes atomically per review with automatic rollback on failure, and safely skips already-stamped projects on re-runs.

Quick Start

Use the rubric-rebackport skill to scan your project tree for unstamped legacy reviews and apply the inferred rubric stamps in one atomic operation.

Frequently Asked Questions about rubric-rebackport

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add missing rubric_id fields to legacy review directories?▼

To add missing rubric identifiers to legacy review directories, use a stamping tool that infers the correct rubric identity from existing metadata and writes rubric_id, rubric_total, and advance_threshold fields directly into _meta.json files.

Can I rescore legacy reviews under a new rubric without modifying the original files?▼

Yes, you can rescore legacy reviews under a new rubric without modifying original files by using an immutable sidecar mode that creates fresh review directories with updated scores, leaving the original legacy review byte-identical for audit trails.

What is the best way to compare legacy review scores across different rubric eras?▼

Comparing legacy review scores across rubric eras requires stamping pre-migration directories with missing rubric metadata like rubric_id and rubric_total to establish a baseline for apples-to-apples comparison.

Does the rubric stamping process support dry runs and rollback on failure?▼

Yes, the rubric stamping process supports dry runs by default and applies changes atomically per review with automatic rollback on failure, while safely skipping already-stamped projects on subsequent re-runs.

What types of review artifacts can be stamped with rescoring metadata?▼

Review artifacts that can be stamped with rescoring metadata include memo, proposal, pub, deck, slides, report, installation, ip-uspto, datasheet, ip-uspto-provisional, and essay review threads within studio project trees.

Why are my legacy review scores incompatible with current rubric thresholds?▼

Legacy review scores are incompatible with current rubric thresholds because pre-migration directories lack the advance_threshold and rubric_total fields needed to align scoring criteria across rubric migrations.