Skip to content

(standardize-repo): Pin the start-of-run question table to QUESTIONS #1856

New issue
New issue
Open
Open
(standardize-repo): Pin the start-of-run question table to QUESTIONS#1856
Labels
ai-generatedCreated or authored by an AI agentarea:standardize-repoThe standardize-repo skill and its standards catalogbugSomething isn't workingcomplexity:sComplexity: small and local; a clear approach across a few filesdomain:standardizationKeeping repos current with conventions: standardize-repo, drift audits, adoptionimpact:mediumImpact: clear benefit to a meaningful share of users or goalslayer:logicBusiness rules, handlers, calculationpriority-ai:p2Priority (AI): worth doing, not blockingrisk:lowRisk: a mistake is contained, caught quickly, and cheap to undotier:economyModel tier: cheapest qualified hosted model first; escalation allowed
Milestone
Standardize-repo fleet runs

Description

@evanharmon1
evanharmon1
opened on Nov 4, 2026

Problem

The start-of-run question table in ai/skills/repo/standardize-repo/SKILL.md restates QUESTIONS in assets/fleet-decisions.py by hand, and nothing pins the two together. A row can be added, dropped or reordered in one and not the other. #1826 was exactly that: label_provisioning existed in QUESTIONS with no row in the table.

Acceptance criteria

  • [CI] A test asserts that the table's keys match QUESTIONS in order.
  • [CI] A test fails when a row is removed from the table.

Verify

git grep -n "QUESTIONS" -- ai/skills/repo/standardize-repo/assets/fleet-decisions.py finds the source of truth; git grep -n label_provisioning -- scripts/test-skills.sh ai/skills/repo/standardize-repo/assets/test-fleet-decisions.py shows whether the table is pinned yet.

Provenance

CodeRabbit nitpick on PR #1849 (review 5773503201, 2026-11-04). That PR's description claimed this assertion, but it was never committed.

Source PR: docs/1826-label-provisioning-question-table
Reviewer: coderabbit
Reviewer badge: unbadged
Adjudicated badge: P2
Priority (AI): p2

Activity

  1. evanharmon1
    added this to the Standardize-repo fleet runs milestone on Nov 4, 2026
  2. evanharmon1
    added
    bugSomething isn't working
    ai-generatedCreated or authored by an AI agent
    layer:logicBusiness rules, handlers, calculation
    domain:standardizationKeeping repos current with conventions: standardize-repo, drift audits, adoption
    area:standardize-repoThe standardize-repo skill and its standards catalog
    impact:mediumImpact: clear benefit to a meaningful share of users or goals
    risk:lowRisk: a mistake is contained, caught quickly, and cheap to undo
    complexity:sComplexity: small and local; a clear approach across a few files
    priority-ai:p2Priority (AI): worth doing, not blocking
    tier:economyModel tier: cheapest qualified hosted model first; escalation allowed
    on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ai-generatedCreated or authored by an AI agentarea:standardize-repoThe standardize-repo skill and its standards catalogbugSomething isn't workingcomplexity:sComplexity: small and local; a clear approach across a few filesdomain:standardizationKeeping repos current with conventions: standardize-repo, drift audits, adoptionimpact:mediumImpact: clear benefit to a meaningful share of users or goalslayer:logicBusiness rules, handlers, calculationpriority-ai:p2Priority (AI): worth doing, not blockingrisk:lowRisk: a mistake is contained, caught quickly, and cheap to undotier:economyModel tier: cheapest qualified hosted model first; escalation allowed

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions