Skip to content

fix: drop the no-op apply action from the five check-only setups - #3583

Open
kyle-sexton wants to merge 2 commits into
mainfrom
chore/drop-noop-apply
Open

fix: drop the no-op apply action from the five check-only setups#3583
kyle-sexton wants to merge 2 commits into
mainfrom
chore/drop-noop-apply

Conversation

@kyle-sexton

Copy link
Copy Markdown
Contributor

Closes #3570

Summary

Phase 1b of the customization-consistency program: the five setups that shipped an apply with no write path (claude-ops, skill-quality, context-budget, repo-hygiene, session-flow) are now check-only, per PLUGIN-PHILOSOPHY's existing Check-only carve-out. Conformance fix to existing doctrine; no owner-doc edit. Independent of the 1a PR (disjoint files); part of the Phase 1 stack.

Fix

Each of the five: description and argument-hint drop apply; the Purpose cites the carve-out and names which class applies (native userConfig / external prerequisites); the former ## apply section becomes a "Reconfiguration guidance" or "Remediation guidance" section that check prints (so no routable guidance was lost); residual "during check or apply" phrasing removed. Eval prompts that invoked setup apply now invoke bare setup; session-flow's eval case renamed; skill-quality and claude-ops README rows and shell blocks updated.

Verification

  • grep -n "^### .*apply\|^## .*apply\|action: apply" over the five SKILL.md files: empty.
  • grep -l "heck-only carve-out" over the five: all five match; the only remaining apply tokens are the carve-out citation sentence.
  • Repo-wide <plugin>:setup apply sweep: no hits outside another session's .claude/worktrees/ (untouched).
  • markdownlint-cli2 over the 7 touched markdown files: 0 issues; all five evals.json parse.
  • skill-quality check-skill (base main): PASS on all five setups (pre-existing advisory WARNs only).

Related

Refs docs/topics/customization-consistency/PLAN.md Phase 1b; carve-out text at docs/PLUGIN-PHILOSOPHY.md "Check-only carve-out". Phase 2a will ratify the drop-apply rule in PLUGIN-PHILOSOPHY's ownership table.

Phase 1b of the customization-consistency program: claude-ops,
skill-quality, context-budget, repo-hygiene, and session-flow setups had
an `apply` action with no write path — every surface they configure is
native userConfig, forbidden settings, or an external prerequisite.
PLUGIN-PHILOSOPHY's Check-only carve-out already says such setups are
check-only, so each now cites the carve-out, drops `apply` from its
description/argument-hint/routing, and folds the former apply guidance
into a remediation/reconfiguration section `check` prints. Eval prompts
and the two READMEs advertising the action follow. Conformance fix to
existing doctrine; no owner-doc edit.

Gates: markdownlint clean, all five evals.json parse, skill-quality
check-skill PASS on all five setups.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014uBXt1tMEReShbpG5gsFUd
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-01T17:19:46.717835Z c2a927d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Patch bumps for claude-ops, skill-quality, context-budget, repo-hygiene,
session-flow with a matching CHANGELOG entry each, per the
changelog-parity gate's published-version-reuse rule.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014uBXt1tMEReShbpG5gsFUd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

setup: drop the no-op apply action from the five check-only setups (Phase 1b)

1 participant