Resolve D35 — description shape stays unconstrained - #38
Merged
Conversation
The question was logged and shipped without being put to the owner, which is backwards: the log is the record of a decision, not the place a decision gets made. Asked, answered (a). Nothing changes in the tree. The two checks that already constrain a description — substantial enough to route on, and not promising what the body does not cover — remain the whole of what is enforced. The entry now says the variation in shape is deliberate rather than drift, so the next full read does not raise it as a defect a third time. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FaQP2WCqeFYH7s9pi1CJ5u
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.
One file. D35 was logged as open and shipped without the question being put to the owner, so the log said a decision was pending when nobody had been asked. It has now been asked and answered.
(a) — leave description shape unconstrained. Nothing changes in the tree.
The two checks that already constrain a description stay the whole of what is enforced:
validate-skills.py)Shape is neither. The entry now records that the variation is deliberate rather than drift — a description that names a sibling skill does so because that pair actually collides, and one that runs capability and trigger together does so because the sentence reads better that way. A template would flatten both. The part a checker can verify, that a sentence beginning
Use thisexists, is the part that matters least: what routes a request is the trigger's content, and no check can read that.Written down so a future full read of the catalog does not raise it as a defect a third time.
On the standing rule that a pull request has to earn its place: this one is documentation only, which normally would not. It exists because an entry marked open that is not open is the same failure as D29 — it sends the next reader down a settled question. If you would rather not carry a PR for it, say so and I will fold the change into the next substantive one instead.
./scripts/check-all.sh— all ten green.🤖 Generated with Claude Code
https://claude.ai/code/session_01FaQP2WCqeFYH7s9pi1CJ5u
Generated by Claude Code