The post-merge follow-ups promise what the prompt queues - #1617
Merged
Conversation
…lity and security The feature line also named readability, but on_before_mergeable_prompt.md has only ever queued the maintainability and security-audit presets — and under the spec-driven thesis, humans read specs while agents work the code, so per-merge readability passes are the one follow-up the methodology de-prioritizes. The readability preset stays in the catalog, on demand and in the maintenance sweep. Approved by the human per the features rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011XvEviGLEJZsp1h6iWzgma
suleimansh
pushed a commit
that referenced
this pull request
Aug 22, 2026
…lity and security (#1617)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the one finding #1614 left for a human call, with that approval now given.
FEATURES-SPEC.mdpromised post-merge quality follow-ups for "maintainability / security / readability", buton_before_mergeable_prompt.mdhas only ever queued the maintainability and security-audit presets — the prompt's history shows no readability line was ever there. Rather than adding a third unattended follow-up per merge (heavy overlap with the maintainability pass, extra quota, duplicate-refactor risk between sibling follow-up PRs), the feature line drops the word: under the spec-driven thesis — humans read specs and stay in control, agents work the code — per-merge readability passes are the one follow-up the methodology itself de-prioritizes.The Readability preset is untouched: it stays in the catalog, on demand from the dashboard and in the periodic maintenance sweep.
One word removed, no code changes; the features edit is human-approved per the rule in
FEATURES-SPEC.md.🤖 Generated with Claude Code
https://claude.ai/code/session_011XvEviGLEJZsp1h6iWzgma
Generated by Claude Code