Skip to content

Scrub branch-named plans in /doc-review - #144

Merged
mattmenefee merged 1 commit into
mainfrom
doc-review-branch-named-plans
Sep 17, 2026
Merged

mattmenefee merged 1 commit into
mainfrom
doc-review-branch-named-plans

Conversation

@mattmenefee

@mattmenefee mattmenefee commented Sep 17, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • The artifact scrub in the user-scope /doc-review now matches *PLAN.md, so it covers branch-named <branch>-PLAN.md plans and still catches a legacy PLAN.md
  • The prose describing what /ship-it publishes now names *-PLAN.md, matching /handoff after Point /handoff at per-branch plan files #142
  • Plans remain root-only: the scrub's find keeps -maxdepth 1

Test plan

  • markdownlint with .markdown-lint.yml passes on home/.claude/commands/doc-review.md
  • The scrub's find expression, run against a scratch directory, matches PLAN.md and doc-review-plans-PLAN.md and skips README.md and sub/x-PLAN.md
  • git grep 'PLAN\.md' on this branch finds no remaining bare PLAN.md reference outside the legacy mentions in handoff.md and the .markdownlintignore glob
  • CI lint passes

Implementation plans are moving from a generic PLAN.md to
<branch>-PLAN.md in the repository root, and /handoff already names
them that way (PR #142). The user-scope /doc-review was missed, and it
shadows a repository's own copy, so its artifact scrub looked only for
a bare PLAN.md and skipped the plan /ship-it posts to the pull request.

The scrub now matches *PLAN.md, which covers branch-named plans and
still catches a legacy PLAN.md. The prose describing what /ship-it
publishes names *-PLAN.md to match.
@mattmenefee mattmenefee self-assigned this Sep 17, 2026
@mattmenefee
mattmenefee merged commit 06227f6 into main Sep 17, 2026
8 checks passed
@mattmenefee
mattmenefee deleted the doc-review-branch-named-plans branch September 17, 2026 08:06
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.

1 participant