Skip to content

feat(docs-naming): hand the file-name rule file choice to /corrections:codify #17162

Description

@kyle-sexton

Parent

Refs #15703
Source: #16029, part 2 of #15729. The list recorded in #16602 gives /docs-naming:generate-file-name-gate the route "call /corrections:codify, presence-gated, with the strongest-first fallback".

Depends on

  • none open. No ecosystem cut item exists for docs-naming.

Outcome

The skill emits a file-name checker (the deliverable the user invoked it for) and, with --rule, a path-scoped rule file beside it; its Purpose argues from its own reasoning why a rule file is "not a substitute" and is only "the option". After this change the gate stays the deliverable, and the choice whether a rule file should also carry the naming rule is handed to /corrections:codify when it is available, with the shared strongest-first fallback when it is not. Emission, refusal, verification and the not-wired report do not change.

Demo: with a corrections stand-in plugin loaded, ask /docs-naming:generate-file-name-gate whether to also write the rule file. The skill emits the gate, names /corrections:codify for the rule-file question, and does not argue the mechanism itself.

Where the text changes

Line numbers as read on main at a483a2c1; they may move. Owner decision of 2026-11-18 on #16029 (option A): the codify call covers only the choice the skill makes beyond its fixed deliverable, which stays as it is.

File and lines Present wording Change
plugins/docs-naming/skills/generate-file-name-gate/SKILL.md:23-31 (Purpose) "A path-scoped rule file is not a substitute. A rule is guidance Claude reads during its own session: it blocks nothing, binds no human editor or other tool, and never runs in CI. ... That is why the gate is the deliverable and the rule is the option." Keep "the gate is the deliverable"; the question whether a rule file should also hold the rule goes to /corrections:codify (gate plus shared fallback). The docs pointer may stay
same file, :113-117 (Gotchas) "A rule file is a pointer surface a repository may deliberately not carry. ... --rule is opt-in for exactly that reason; offer it and let the operator decide." Keep --rule opt-in; the offer names the codify route

Call form: /corrections:codify "<the naming rule>".

Decisions

Key interfaces

  • "A skill that carries no ladder copy calls /corrections:codify, presence-gated, with a two-sentence strongest-first fallback. Only a skill that applies its own selection rule holds a synced copy and gets a row in the ladder's Selection rules table." (List enforcement-placing skills and give each one route to the ladder #15729)
  • The seam-phrasing convention: an availability gate, a stated fallback beside it, the plugin named and never the marketplace.

Done when

  • The Purpose and the --rule gotcha hand the rule-file choice to /corrections:codify behind the availability gate, followed by the shared fallback, and no longer argue the mechanism in the skill's own words.
  • emit-gate.sh, the templates and the completion criteria are unchanged.
  • The skill gains no ladder copy or Selection rules row, and no rung list is restated.
  • The pull request body names the existing case whose run reads the changed text (candidates: gate-not-replaced-by-rule, gate-emits-and-names-unwired), or says none does. The lane runs no eval.
  • A changelog fragment under .changes/docs-naming/ describes the change.
  • AC10: no new enforcement-placing skill is added here.
  • Open the pull request with Closes this issue in its body, then stop: the lane adds no label.

Host steps (eval case, tracker-output quote) are tracked in #17200.

After the pull request opens (host session, not the lane)

The pull request stays held with do-not-merge for the eval; a host session runs only the eval and posts its record; the merge lane releases the hold when the record matches the head.

  • Hold line: the hub's sweep (or a host session) adds do-not-merge and posts, from a listed human's account, a comment with the line <!-- pr-hold reason=eval --> on a line of its own.
  • Run budget. List enforcement-placing skills and give each one route to the ladder #15729 asks for "that skill's cases on the opus and sonnet aliases, three runs per side, and no more than 240 runs per plugin". The owner decision of 2026-11-16 in the owner-decisions record (hop 4 Q15, which names List enforcement-placing skills and give each one route to the ladder #15729, amended by hop 7 Q3) replaces the run counts: per changed skill, one targeted before-and-after case on sonnet at 3 runs a side; opus runs only to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first. Select cases with --case, use --runs 3 and a --max-cost-usd ceiling, and start no batch after a usage-limit error. Ceiling for this plugin: 1 skill x (3 smoke + 6 sonnet + 6 opus confirm) = 15 runs, under the parent's 240.
  • Control: the replaced argument is a partial cut, so the pull request body carries a detection-control result. No paired no-loss compare (#15703 comment 6906800940).
  • On a LOSS reading: a trace read of each dropped case and an opus confirm; only a loss traced to the changed text counts.
  • Record: the verdict and the control result go into the pull request body. When the run is VALID and shows no loss, the host session posts, from a listed human's account, a comment with the line <!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> --> naming the current head, keeping "do not merge" and do-not-merge out of that comment (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). A loss or a run that is not VALID leaves the hold in place; say so on the pull request.
  • Release: pr-merge's scheduled step "Release eval holds whose record matches the head" removes do-not-merge once that record names the current head and no other hold stands. A push after the record needs a new record.

Out of scope

  • The emitted checker, its suite and the rule template.
  • The other docs-naming skills.

Related

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 18, 2026
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 18, 2026
  3. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none
    Blast radius: two passages of one skill's SKILL.md (Purpose and the --rule gotcha) plus a changelog fragment; read by Claude when it runs /docs-naming:generate-file-name-gate.
    Reversible: yes; revert the text edit and the fragment.
    Open questions: none
    I understood this as a bounded text change. The gate stays the deliverable. The question of whether a rule file should also carry the naming rule goes to /corrections:codify behind an availability gate, with the shared strongest-first fallback. --rule stays opt-in, and the emitter, templates and completion criteria do not change. The issue's text answers the scope and design questions, so none are open. The eval-case and tracker-output items are host steps tracked in #17200; they do not block the text change. I found no open duplicate and did not check the merged-pulls list for an existing fix.

    Automated triage. A maintainer reviews it.

  4. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 18, 2026
  5. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 4 (tracker-output: "The pull request body quotes the sentence that picked a mechanism from a priv..."), item 5 (eval: "One new eval case loads a corrections stand-in plugin, in the shape of sessio..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the host queue (host-run). Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  6. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"89e9ecf3baa80778ec810d504f6885e07e2943367fb78764411356122f53d0ea","body_sha256":"bbfee67d71a7fe8938d500537e1f89e4b18d7d8de8f451bbae55ae600cf931a2"}

  7. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"89e9ecf3baa80778ec810d504f6885e07e2943367fb78764411356122f53d0ea","body_sha256":"bbfee67d71a7fe8938d500537e1f89e4b18d7d8de8f451bbae55ae600cf931a2"}

  8. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor
    No description provided.
  9. github-actions commented on Nov 19, 2026

    @github-actions
    Contributor
    No description provided.
  10. melodic-automation-lanes commented on Nov 19, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.

  11. melodic-automation-lanes commented on Nov 19, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44433847384, the work-resolve-issue run that agent-ready started, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-19T01:47:41Z. work-unblock has now removed and added agent-ready back to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or the kill-switch wait.

  12. github-actions commented on Nov 19, 2026

    @github-actions
    Contributor
    No description provided.
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

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Type

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions