Skip to content

HITL: Skill to draft WAI changelog and run approve-rule #73

Description

@WilcoFiers

Parent

#60

Type

HITL. An agent can draft the changelog and drive the script, but a person must confirm the bullets before anything is pushed to w3c/wcag-act-rules. This is not a weekly bot job.

Why this is not AFK

The published changelog is the WAI version list on rule-versions.yml (rendered on the rule page). Existing entries are short, user-facing bullets (“Account for whitespace in the applicability”, “Account for focus redirects in ‘focusable’ definition”). They collapse many commits, skip formatter/last_modified noise, and name the effect of a glossary change on that rule.

Classifier git subjects on the act-board issue are raw material, not that text. Do not dump them into changes:.

What to build

A Cursor skill (in act-rules/act-rules.github.io, next to write-act-rule) that:

  1. Takes a ruleId that is Approved, unpublished changes (or first-time Proposed, reviewable).
  2. Reads the board snapshot row, commits since approvalIsoDate, and a real diff of proposed vs last approved index.md (prefer that diff over commit subjects when they disagree).
  3. Drafts a short YAML changes: list in existing WAI voice (typically 2–6 bullets), plus a one-paragraph AGWG PR body. Separate editorial from substantive. Phrase definition-only commits as they affect this rule.
  4. Stops for confirmation. Do not run the script until the user accepts or edits the bullets.
  5. First-time approval: no changelog. Re-approval: refuse to proceed with an empty list.
  6. After confirm, run the extended approve-rule path from AFK: Extend approve-rule for re-approval, one branch per rule #64 (changelog passed as --change flags or a small YAML file — not a workflow_dispatch text box as the authoring surface).

Do not open tens of PRs. One rule per invocation. Weekly board sync must not call this.

Acceptance criteria

Blocked by

Activity

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions